bd2b6c40bc
11513: internal: Expand the derive attribute into a pseudo expansion r=Veykril a=Veykril Quoting my comment: > We generate a very specific expansion here, as we do not actually expand the `#[derive]` attribute > itself in name res, but we do want to expand it to something for the IDE layer, so that the input > derive attributes can be downmapped, and resolved as proper paths. > This is basically a hack, that simplifies the hacks we need in a lot of ide layer places to > somewhat inconsistently resolve derive attributes. > > As such, we expand `#[derive(Foo, bar::Bar)]` into > ``` > #[Foo] > #[bar::Bar] > (); > ``` > which allows fallback path resolution in hir::Semantics to properly identify our derives. > Since we do not expand the attribute in nameres though, we keep the original item. > > The ideal expansion here would be for the `#[derive]` to re-emit the annotated item and somehow > use the input paths in its output as well. > But that would bring two problems with it, for one every derive would duplicate the item token tree > wasting a lot of memory, and it would also require some way to use a path in a way that makes it > always resolve as a derive without nameres recollecting them. > So this hacky approach is a lot more friendly for us, though it does require a bit of support in > [`hir::Semantics`] to make this work. Co-authored-by: Lukas Wirth <lukastw97@gmail.com> |
||
|---|---|---|
| .cargo | ||
| .github | ||
| .vscode | ||
| assets | ||
| bench_data | ||
| crates | ||
| docs | ||
| editors/code | ||
| lib | ||
| xtask | ||
| .gitattributes | ||
| .gitignore | ||
| bors.toml | ||
| Cargo.lock | ||
| Cargo.toml | ||
| LICENSE-APACHE | ||
| LICENSE-MIT | ||
| PRIVACY.md | ||
| README.md | ||
| rustfmt.toml | ||
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.
Work on rust-analyzer is sponsored by
Quick Start
https://rust-analyzer.github.io/manual.html#installation
Documentation
If you want to contribute to rust-analyzer or are just curious about how things work under the hood, check the ./docs/dev folder.
If you want to use rust-analyzer's language server with your editor of choice, check the manual folder. It also contains some tips & tricks to help you be more productive when using rust-analyzer.
Security and Privacy
See the corresponding 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
- Website: https://rust-analyzer.github.io/
- Metrics: https://rust-analyzer.github.io/metrics/
- API docs: https://rust-analyzer.github.io/rust-analyzer/ide/
- Changelog: https://rust-analyzer.github.io/thisweek
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.