-
Notifications
You must be signed in to change notification settings - Fork 13k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create .vscode
directory in x.py setup
#107703
Comments
I also considered checking |
I think this is fine so long as And probably if .vscode/settings.json already exists you should just always print instead of trying to modify it in-place (modifying sounds hard since that file allows comments, and i would be pretty mad if they got overwritten). |
👍 sounds good - we do something like that today for the pre-push hook: Lines 375 to 389 in 4aa6afa
|
…yn514 Allow automatically creating vscode `settings.json` with `x setup` Closes rust-lang#107703
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 rerunningx setup
intidy
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 :/
The text was updated successfully, but these errors were encountered: