You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.
the description says: Disable usage of rustup and use rustc/rls from PATH
So in theory it could work installing only rustc and rls. I think the default is good as rustup is really easy to install and the extension uses it to install the rest of things.
The go command, if I remember correctly, bundles up a bunch of things that Rust has broken out into individual utilities; consider installing rustup like having the go get subcommand. (Not the best comparison, but it gets the idea across.) It's part of the core language tooling, so it shouldn't cause you any pain (unless you are, for some reason, really strapped on disk space) to install it.
Bear in mind, you don’t needrls to try out Rust. All you really need is rustc (and cargo probably) so if you want more tooling, you’re just going to have to install the tool chain manager if you don’t want to jump through some awkward hoops.
The go command, if I remember correctly, bundles up a bunch of things that Rust has broken out into individual utilities;
Really the go command is equivelent to cargo. My biggest beef with cargo is installing toolchains and toolsinto $HOME. I don't want them there and it's harder to control versioning of my system which includes non-rust utilities as well.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It is not a good idea to install too many thins for new user.
I'm a golang user. I just want to have a try with rust. But I need to install too many things. It makes me give up.
The text was updated successfully, but these errors were encountered: