Google Git
Sign in
fuchsia / third_party / github.com / rust-lang / rust-analyzer / 1251660bb2bc73872d2d12c3a9f3081852136b6d
commit1251660bb2bc73872d2d12c3a9f3081852136b6d[log] [tgz]
authorJakub Beránek <berykubik@gmail.com>Mon Jul 14 11:04:52 2025 +0200
committerGitHub <noreply@github.com>Mon Jul 14 11:04:52 2025 +0200
tree754e19dfe080d2b340340be1c77ea052bba8bf2c
parentbcc0a79a810df7f6caebaa56bdd4c2602289194a [diff]
parentd0188bdb3de92fb2f90817719ab52178bd4b2b8f [diff]
Rollup merge of #143681 - RalfJung:bootstrap-miri-rebuilds, r=Kobzol

bootstrap/miri: avoid rebuilds for test builds

When building Miri in its own repo, we always build with `--all-targets`:
https://github.com/rust-lang/rust/blob/a00961269107703772c4e8f071f0accbe0f1a7e5/src/tools/miri/miri-script/src/util.rs#L167-L174
This saves a bunch of time since some of Miri's dependencies get more features enabled by some of Miri's dev-dependencies, and they all get built twice otherwise if you do `cargo build && cargo test` (which is typically what you end up doing inside `./miri test` and also inside `./x test miri`).

This applies the same approach to bootstrap, drastically reducing the edit-compile cycle for Miri work here. :)
tree: 754e19dfe080d2b340340be1c77ea052bba8bf2c
  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.