Google Git
Sign in
fuchsia/third_party/github.com/rust-lang/rust-analyzer/93bff1c864613567d9c4936cf82a5f17b60e763e
commit
93bff1c864613567d9c4936cf82a5f17b60e763e
[log]
author
Jonathan Brouwer <jonathantbrouwer@gmail.com>
Fri Mar 06 18:49:50 2026 +0100
committer
GitHub <noreply@github.com>
Fri Mar 06 18:49:50 2026 +0100
tree
631a65ef919d5f898d77bccb18e07bb1d1229636
parent
a5789ffbf4037f86a604cef35b423f760cd488de [diff]
parent
b32496f94d4b338fa4c424368539bf22c8f78138 [diff]
Rollup merge of #153230 - jieyouxu:rustfmt-reviewers-for-rustfmt, r=ytmimi

Roll rustfmt reviewers for in-tree rustfmt

Noticed in https://github.com/rust-lang/rust/pull/153229#issuecomment-3977482140, where because `src/tools/rustfmt` has no corresponding `[assign.owners]` entry, it rolls one of the `fallback` reviewers (Mark and me) which is needless indirection, since if it rolls to Mark, Mark will have to reroll again.

This _can_ also be

```toml
"/src/tools/rustfmt" = ["rustfmt", "rustfmt-contributors"]
```

which corresponds to https://github.com/orgs/rust-lang/teams/rustfmt and https://github.com/orgs/rust-lang/teams/rustfmt-contributors respectively. I will double-check with triagebot team if we can use review rotation toggles for `rust-lang/rust` in-tree `rustfmt` specifically.

Discussion: [#t-rustfmt > review queue tracking for rust-lang/rust in-tree rustfmt](https://rust-lang.zulipchat.com/#narrow/channel/357797-t-rustfmt/topic/review.20queue.20tracking.20for.20rust-lang.2Frust.20in-tree.20rustfmt/with/576498516)

### Unresolved question

- ~~Do we want to start everyone off as off-rotation? Or on-rotation? I plan to start conservatively by preserving existing effective status, which is everyone off-rotation.~~ We will match existing defaults, with everyone starting off as off-team-rotation.

r? @ytmimi
tree: 631a65ef919d5f898d77bccb18e07bb1d1229636
  1. .cargo/
  2. .github/
  3. .vscode/
  4. assets/
  5. bench_data/
  6. crates/
  7. docs/
  8. editors/
  9. lib/
  10. xtask/
  11. AGENTS.md ⇨ CLAUDE.md
  12. .codecov.yml
  13. .editorconfig
  14. .git-blame-ignore-revs
  15. .gitattributes
  16. .gitignore
  17. .typos.toml
  18. Cargo.lock
  19. Cargo.toml
  20. CLAUDE.md
  21. clippy.toml
  22. CONTRIBUTING.md
  23. josh-sync.toml
  24. LICENSE-APACHE
  25. LICENSE-MIT
  26. PRIVACY.md
  27. README.md
  28. rust-version
  29. rustfmt.toml
  30. triagebot.toml
README.md

rust-analyzer is a language server that provides IDE functionality for writing Rust programs. You can use it with any editor that supports the Language Server Protocol (VS Code, Vim, Emacs, Zed, etc).

rust-analyzer features include go-to-definition, find-all-references, refactorings and code completion. rust-analyzer also supports integrated formatting (with rustfmt) and integrated diagnostics (with rustc and clippy).

Internally, rust-analyzer is structured as a set of libraries for analyzing Rust code. See Architecture in the manual.

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.