Rustup VS rust-analyzer

I got it to finally work by following this

If you are someone actively using such relative-path toolchains, please contact us (Discord / Github issues).

We had a snap package; we removed it in mid 2022

I don't know. The PR references prior discussion without a link, so it may have been private.

As long as he doesn't put hidden folders in your root like rust. https://github.com/rust-lang/rustup/issues/341

I think you're being upvoted by folks who don't know better, which is a shame because you're making things up :/. The telemetry feature in rustup kept everything local and never "pinged home". And you had to enable it with a command `rustup telemetry enable`. And it just logged JSON files at the path you mentioned. By 2019, the feature was disabled (see: https://github.com/rust-lang/rustup/issues/341 ) because no one worked on it and it just gathered bugs.

FWIW, there is a proposal to add telemetry to LLVM [0] and Rust used to have telemetry [1], both off by default. Some things in the node.js world have telemetry enabled by default, like Next.js [3].

Some people are posting here as if this as already decided -- AFIACT, that's not the case. It's not even a formal proposal yet, and the stated intent was to start a conversation around something concrete. (For context, this is standard for how I've seen the Go project approaches large topics, including for example I think there were something like ~8 very detailed generics design drafts from the core Go team over ~10 years).

It sounds like the Go team is going to take some time to look into some of the alternative approaches suggested in the feedback collected so far.

In any event, this is obviously a topic people are very passionate about, especially opt-in vs. opt-out, but I guess I would suggest not giving up hope quite yet.

[0] https://discourse.llvm.org/t/rfc-lldb-telemetry-metrics/6458...

[1] https://github.com/rust-lang/rustup/issues/341

[2] https://nextjs.org/telemetry

Rust (Specifically Rust Up) seems to have planned to include telemetry but they paused and cancelled the decision, possibly after implementing it initially.

https://github.com/rust-lang/rustup/issues/341 and rust installation uses telemetry

go build 3.62s user 0.76s system 171% cpu 2.545 total

I was looking forward to parallel front-end[4], but I have not seen any improvement for these small changes.

[1]: https://github.com/rust-lang/rust-analyzer

For example, intelephense can show diagnostics in real time, there is no need to save the file to get new diagnostics. But rust-analyzer, the language server for rust, can only update diagnostics after saving the file.

6. Rust Analyzer

The rust-analyzer readme suggests you go here for support request. But even there, you'll need to provide more details to get useful help.

For example: https://github.com/rust-lang/rust-analyzer/blob/master/docs/...

> If you create an LSP, it will work best in VS Code.

Any editor can work just as well as (or even better than) VS Code.

So, apparently the reason why rust-analyzer, the LSP server for Rust does not have persistent caching is because it would make "optimizing initial passes less important".

All I want to know is: Will it have a build configuration pulldown?

I am not a Rust dev. It surely looks great.

However, from what I understand it seems to supply just a parser separate from the Rust compiler (https://github.com/rust-lang/rust-analyzer/tree/master/crate...) trying to keep up with Rust‘s development. So, in principle, it could have been just another treesitter parser plugin, too.

So, again, the LSP framework does not directly provide any magical benefit over a static parsing framework. All the semantic analysis capabilities stem from a good parser.

rust-analyzer > manual > helix > binary > rustup component add rust-analyzer