The renderer benchmarks drain the main queue to quiescence before each measured frame, so a task that yields and re-queues itself (an idle sweep, a poller) runs to completion inside a single measured frame — or keeps the benchmark spinning forever. Real platforms don't work that way: macOS's main-queue drain only runs the items present when the drain starts, Linux runs one runnable per calloop idle callback, and Windows drains under a 10ms budget before servicing paint messages — frames always get a chance to preempt. So `run_ready_main_tasks` now only runs the tasks that were queued when servicing began, letting self-re-queuing work advance one batch per frame like it would under a real run loop, and `BenchAppContext` grows a `run_until` (wrapping the dispatcher primitive task benchmarks already use) so setup code can pump the app until a condition holds without settling to idle first. 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.