029d08350e60f6f6f0d619e2fa26efd0e7860cad
Closes #20001 the old outline was *weird* for many reasons so ill just show it with a hodgepodge of zig declarations before:  after:  why were values shown? why werent `var`s or modifiers like pub, const, export? it was very odd to me and inconsistent with other languages. i chose to leave out unnamed tests, it just seemed like noise to me since they werent distinct but i can easily revert that unfortunately there seems to be a bug upstream which causes those `t`/`f` decls to show 2 things https://github.com/tree-sitter-grammars/tree-sitter-zig/issues/3 im very new to treesitter and queries so i really havent looked over the rest of the stuff here, other than outline theyre unmodified please lmk if theres anything wrong Release Notes: - Changed upstream treesitter grammar for zig
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS and Linux you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- Windows (tracking issue)
- Web (tracking issue)
Developing Zed
- Building Zed for macOS
- Building Zed for Linux
- Building Zed for Windows
- Running Collaboration Locally
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
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 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.
Description
GPUI – Community Edition maintained by Oak Team
https://gpui-ce.github.io/
258 MiB
Languages
Rust
95.6%
WGSL
1.2%
Metal
1.1%
HLSL
1.1%
Python
0.6%
Other
0.3%