Tracking issue for known bugs on rust-lang/rust

[jonas-schievink]

The Rust monorepo is "special" and uses a lot of idiosyncrasies, so rust-analyzer doesn't work very well there. We would like to fix that, because it's The Rust Repo™ and we'd like compiler/libstd hackers to have a good time with rust-analyzer. This issue tracks any known problems while working on that repo.

Note: Before filing a bug, make sure that you're using the configuration recommended in the rustc dev guide.

List of issues:

• Prelude not imported in rustc_span #8815
• In rustc workspace, cranelift errors are ignored #8937
• rust-lang/rust: guide recommends disabling proc macro server. we should make it work #9201
• rust-lang/rust: "file not included in module tree" in libcore, broken go to definition #9203
• x.py in rust-lang/rust does not like being called by rust-analyzer #9349
• unresolved-macro-call: vec! in library/proc_macro/src/bridge #9446

[lf-]

#9349 also

[jyn514]

Please also track supporting sysroot crates (#6842 is an example, there may be others).

[jonas-schievink]

That apparently works with the right configuration, so I closed it