-
Notifications
You must be signed in to change notification settings - Fork 893
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
VSCode + RLS install is a mess #1301
Comments
Same problem, I have update nightly toolchain to |
Same it just disappeared |
Same for rustfmt-preview. I think there's some kind of upstream problem causing some components to be skipped with the nightly builds. I've been using |
Releases of additional tools are referenced to be built and included in nightly rust releases. If the additional tool's, ie rls-preview's, latest release does not build with latest nightly-rust that tool will be missing. This is an unfortunate fact of nightly life, Rls is fragile to rustc changes and nightly updates can include changes to the compiler. The long solution is the stabilization of Rls meaning normal development will take place on stable-rust. Until then we have to handle potential nightly absences of Rls.
|
See also rust-lang/rls#611 (comment) |
This gets even worse if you want to use clippy. I haven't found any nightly that is usable if I want to use clippy, fmt, and rls. |
Its all still a hot mess even after two years. Why is this so dysfunctional? |
AFAIK, the only rustup-related issue here was that it would allow you to upgrade to a nightly rustc which was built without the RLS. This has been fixed. @elliottneilclark @DanielJoyce |
OBS: I don't see the usual C++ debug profile, nor the dialog prompting me to select
WTF?
I think all of this amounts to the same thing, see title. Sorry.
The text was updated successfully, but these errors were encountered: