zld VS rust-analyzer

Well sold has a few extra features, namely macOS support, so I assume if you're a developer on a MacBook, and you want to link faster, you'd need to use sold. Although to be honest, I didn't see much difference between soldon macOS and zld.

Have you tried zld (https://github.com/michaeleisel/zld) for linking?

The default linker is single-threaded so, unless you're on a platform where you can use a fancier multi-threaded linker like mold or zld, single-core performance will dominate for the final linking step.

- If it's not a release build that needs to be verified-good, consider using `mold` to link your builds and test binaries: https://github.com/rui314/mold --- it is much faster than lld or gold. For mac users there is https://github.com/michaeleisel/zld but mostly if you care about build times you need to get off macOS somehow.

Zld: Drop-in, faster version of Apple's linker\ (0 comments)

There is also zld (https://github.com/michaeleisel/zld) which might get you a further speed up.

as an alternative linker for Rust as an example:

https://github.com/michaeleisel/zld#if-using-rust

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