mirror of
https://github.com/zed-industries/zed.git
synced 2026-10-19 02:54:11 +00:00
original uri https://github.com/zed-industries/zed
https://zed.dev
a2a92fe7c4
## Summary I'm building a single-threaded web app on `gpui_web`, served as static files, and I can't build it on stable Rust. `gpui_web`'s default feature `multithreaded` pulls in `wasm_thread`, which needs the unstable `stdarch_wasm_atomic_wait` feature gate. With `default-features = false` the crate checks clean on stable, but `gpui_platform` depends on `gpui_web` with defaults, so using the platform helper on wasm, including its `single_threaded_web()`, brings the feature and nightly back. Threads in a browser also need COOP/COEP headers and `build-std`, so for a static site the single-threaded platform is the normal case. This declares `gpui_web` without default features in the workspace and has `gpui_platform` forward `multithreaded`, on by default. Nothing changes unless a consumer opts out with `default-features = false`. `hello_web` keeps its threads since it takes the helper's defaults. ## Testing In this workspace, on stable: `cargo check -p gpui_platform --target wasm32-unknown-unknown --no-default-features`. On nightly, the same with defaults, which is the status quo path. `cargo check -p gpui_platform` on the host, since `gpui_web` is only a wasm dependency and the feature reference must still be accepted there. And `cargo tree -p gpui_platform -e features --target wasm32-unknown-unknown` with and without `--no-default-features`, showing `wasm_thread` present and then absent. ## Self-review - [x] I've reviewed my diff for quality, security, reliability, and performance. - [ ] UI changes follow the [checklist](https://zed.dev/docs/development/ui-checklist). (No UI change.) - [ ] Tests cover the new or changed behavior. (A manifest change, the tree and check commands above are the test.) I used an AI assistant, which helped me trace where the feature gets switched on. I've reviewed the changes and verified the checks above pass on my machine. Release Notes: - N/A - [GPUI] The multithreaded feature for `gpui_web` can now be forwarded Co-authored-by: Lukas Wirth <lukas@zed.dev> |
||
|---|---|---|
| .agents/skills | ||
| .cargo | ||
| .cloudflare | ||
| .config | ||
| .factory | ||
| .github | ||
| .wezel | ||
| .zed | ||
| assets | ||
| ci | ||
| crates | ||
| docs | ||
| extensions | ||
| legal | ||
| nix | ||
| script | ||
| tooling | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .prettierrc | ||
| .rules | ||
| AGENTS.md | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CLAUDE.md | ||
| clippy.toml | ||
| CODE_OF_CONDUCT.md | ||
| compose.yml | ||
| CONTRIBUTING.md | ||
| corgi.toml | ||
| default.nix | ||
| Dockerfile-collab | ||
| Dockerfile-collab.dockerignore | ||
| Dockerfile-cross.dockerignore | ||
| Dockerfile-distros | ||
| Dockerfile-distros.dockerignore | ||
| flake.lock | ||
| flake.nix | ||
| GEMINI.md | ||
| LICENSE-APACHE | ||
| LICENSE-GPL | ||
| Procfile | ||
| Procfile.web | ||
| README.md | ||
| rust-toolchain.toml | ||
| rustfmt.toml | ||
| shell.nix | ||
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.