## Summary A singleton multibuffer has one excerpt, from its buffer's min anchor to its max anchor. Multibuffer coordinate conversions, such as `offset_to_point` and `Anchor::to_point`, resolve both ends with `BufferSnapshot::summary_for_anchor`. For the min anchor, it seeks a rope cursor to sum an empty range. For the max anchor, it seeks a rope cursor to the end and adds up subtree summaries on the way, though the rope's root already stores the total. `summary_for_anchor` now returns zero for the min anchor and the root summary for the max anchor, as `summaries_for_anchors_with_payload` already does. Time per call on a singleton multibuffer, averaged over 10,000 random positions. Release build pinned to one core, Ryzen 7 9800X3D, median of 5 alternating runs: | Call | 1k lines | 10k lines | 100k lines | |---|---|---|---| | `offset_to_point` | 176 → 61 ns | 229 → 75 ns | 289 → 105 ns | | `point_to_offset` | 187 → 67 ns | 235 → 84 ns | 299 → 116 ns | | `clip_point` | 180 → 71 ns | 229 → 87 ns | 290 → 117 ns | | `Anchor::to_point` | 349 → 241 ns | 453 → 306 ns | 560 → 379 ns | After was faster in every run. ## Testing - `test_summaries_for_unordered_anchors` and its `_across_chunks` variant already resolve the min and max anchors with `summary_for_anchor`. They fail if either case returns the wrong summary, including when the two are swapped. - `cargo test -p text -p rope -p multi_buffer -p editor` passes. - `./script/clippy -p text` passes. ## Self-review - [x] I've reviewed my diff for quality, security, reliability, and performance. - [x] UI changes follow the [checklist](https://zed.dev/docs/development/ui-checklist). - [x] Tests cover the new or changed behavior. Release Notes: - N/A
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).
Other platforms are not yet available:
- Web (tracking discussion)
Developing Zed
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
Zed source code is licensed primarily under GPL-3.0-or-later, with Apache-2.0 components where marked.
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.
Sponsorship
Zed is developed by Zed Industries, Inc., a for-profit company.
If you’d like to financially support the project, you can do so via GitHub Sponsors. Sponsorships go directly to Zed Industries and are used as general company revenue. There are no perks or entitlements associated with sponsorship.