Code at the speed of thought – Zed is a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Find a file
Marshall Bowers bf666af3a2
Deny all Clippy warnings (#8720)
This PR makes Clippy deny all warnings across the workspace.

We now enumerate all of the rules that have violations and temporarily
allow them, with the goal being to drive the list down over time.

On Windows we don't yet use `--deny warnings`, as the Windows build
still has some warnings.

Release Notes:

- N/A
2024-03-02 15:51:01 -05:00
.cargo Add cargo xtask clippy (#8722) 2024-03-02 14:46:02 -05:00
.config
.github Deny all Clippy warnings (#8720) 2024-03-02 15:51:01 -05:00
.zed
assets
crates Deny all Clippy warnings (#8720) 2024-03-02 15:51:01 -05:00
docs
extensions/gleam Add initial support for defining language server adapters in WebAssembly-based extensions (#8645) 2024-03-01 16:00:55 -08:00
script Add cargo xtask clippy (#8722) 2024-03-02 14:46:02 -05:00
tooling/xtask Deny all Clippy warnings (#8720) 2024-03-02 15:51:01 -05:00
.dockerignore
.gitattributes
.gitignore Add initial support for defining language server adapters in WebAssembly-based extensions (#8645) 2024-03-01 16:00:55 -08:00
.gitmodules
.mailmap
Cargo.lock Add cargo xtask clippy (#8722) 2024-03-02 14:46:02 -05:00
Cargo.toml Add cargo xtask clippy (#8722) 2024-03-02 14:46:02 -05:00
CODE_OF_CONDUCT.md
CONTRIBUTING.md
debug.plist
docker-compose.sql
docker-compose.yml
Dockerfile
LICENSE-AGPL
LICENSE-APACHE
LICENSE-GPL
livekit.yaml
Procfile
README.md
rust-toolchain.toml
typos.toml

Zed

CI

Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.

Installation

You can download Zed today for macOS (v10.15+).

Support for additional platforms is on our roadmap:

For macOS users, you can also install Zed from Homebrew:

brew install zed

Developing Zed

Contributing

See CONTRIBUTING.md for ways you can contribute to Zed.

Licensing

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 specified error for a crate you've created? If so, add publish = false under [package] in your crate's Cargo.toml.
  • Is the error failed to satisfy license requirements for 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 the accepted array in script/licenses/zed-licenses.toml.
  • Is cargo-about unable to find the license for a dependency? If so, add a clarification field at the end of script/licenses/zed-licenses.toml, as specified in the cargo-about book.