Google Git
Sign in
fuchsia / third_party / github.com / rust-lang / rust-analyzer / ad989509709189e2d5b93b8d4c016b2f7808561e
commitad989509709189e2d5b93b8d4c016b2f7808561e[log] [tgz]
authorbors <bors@rust-lang.org>Tue Jul 01 02:22:42 2025 +0000
committerbors <bors@rust-lang.org>Tue Jul 01 02:22:42 2025 +0000
tree252f35a1ac7ec1629a229d53efbfd9f625603651
parent53291632cfeb66e518f8ec63de6dbbb02af6eca8 [diff]
parent88d4ce161e18e58e368797d1b43f734ebc0e61af [diff]
Auto merge of #141875 - nnethercote:ByteSymbol, r=petrochenkov

Introduce `ByteSymbol`

It's like `Symbol` but for byte strings. The interner is now used for both `Symbol` and `ByteSymbol`. E.g. if you intern `"dog"` and `b"dog"` you'll get a `Symbol` and a `ByteSymbol` with the same index and the characters will only be stored once.

The motivation for this is to eliminate the `Arc`s in `ast::LitKind`, to make `ast::LitKind` impl `Copy`, and to avoid the need to arena-allocate `ast::LitKind` in HIR. The latter change reduces peak memory by a non-trivial amount on literal-heavy benchmarks such as `deep-vector` and `tuple-stress`.

`Encoder`, `Decoder`, `SpanEncoder`, and `SpanDecoder` all get some changes so that they can handle normal strings and byte strings.
tree: 252f35a1ac7ec1629a229d53efbfd9f625603651
  1. .cargo/
  2. .github/
  3. .vscode/
  4. assets/
  5. bench_data/
  6. crates/
  7. docs/
  8. editors/
  9. lib/
  10. xtask/
  11. .editorconfig
  12. .git-blame-ignore-revs
  13. .gitattributes
  14. .gitignore
  15. .typos.toml
  16. Cargo.lock
  17. Cargo.toml
  18. clippy.toml
  19. CONTRIBUTING.md
  20. LICENSE-APACHE
  21. LICENSE-MIT
  22. PRIVACY.md
  23. README.md
  24. rust-version
  25. rustfmt.toml
  26. triagebot.toml
README.md

rust-analyzer is a modular compiler frontend for the Rust language. It is a part of a larger rls-2.0 effort to create excellent IDE support for Rust.

Quick Start

https://rust-analyzer.github.io/book/installation.html

Documentation

If you want to contribute to rust-analyzer check out the CONTRIBUTING.md or if you are just curious about how things work under the hood, see the Contributing section of the manual.

If you want to use rust-analyzer's language server with your editor of choice, check the manual. It also contains some tips & tricks to help you be more productive when using rust-analyzer.

Security and Privacy

See the security and privacy sections of the manual.

Communication

For usage and troubleshooting requests, please use “IDEs and Editors” category of the Rust forum:

https://users.rust-lang.org/c/ide/14

For questions about development and implementation, join rust-analyzer working group on Zulip:

https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Frust-analyzer

Quick Links

License

rust-analyzer is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0).

See LICENSE-APACHE and LICENSE-MIT for details.