Description
Right now, .vscode needs to be configured anew for each workspace and person working on the compiler. We do document the recommended settings in https://rustc-dev-guide.rust-lang.org/building/suggested.html#configuring-rust-analyzer-for-rustc, but it's annoying to have to copy-paste it each time. It would be nice if x setup
created those files for you automatically.
Ideally we would even version the config (maybe with a stamp file so it's not in the settings.json
file itself) and suggest rerunning x setup
in tidy
if the config in .vscode gets outdated.
cc https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Frust-analyzer/topic/False.20error.20report.20for.20.60rust-analyzer.28private-field.29.60 - it might be the case that the settings vary depending on the part of the compiler you're working on? I would really hate for that to be the case, but having per-profile .vscode setup might be one way to make it less painful :/