[steveklabnik]

Have you seen rust-analyzer? That’s effectively it.

[Waterluvian]

No I don't think I was aware of this. I've been playing with VSCode -> RLS Plugin -> RLS. It looks like this is not that, so I'm pretty excited to check it out.

Thanks for sharing!

[steveklabnik]

Great!

For anyone else who hasn't: https://rust-analyzer.github.io/ and https://ferrous-systems.com/blog/rust-analyzer-2019/

[dralley]

Unfortunately you still have to compile it from source instead of install an extension from the store, and there's no autoupdate.

But the experience is vastly better. I deleted RLS immediately. And it's not that hard to install either.

[Waterluvian]

This is part of why I think I never discovered rust-analyzer. I first looked at what's most popular in the VSCode plugin library and found RLS. I then browser searched for alternatives and kept finding RLS. I think I concluded that RLS was all there was.

[Fiahil]

Thanks for sharing ! I'll stick to RLS for the time being, because I'd like to see it improved, but not replaced.

[dralley]

rust-analyzer is effectively RLS 2.0 -- rust-analyzer development happens on the official RLS 2.0 working group communication channels. Assuming they don't "replace" the RLS name, the most likely outcome is replacing large amounts of code en-masse with rust-analyzer code.

https://rust-lang.github.io/compiler-team/working-groups/rls...

[rapsey]

Analyser runs at 400% cpu constantly for me.

[jayflux]

Have you tried a recent build? They fixed a few issues around cpu usage over the past few months

[jayflux]

I’ve moved from RLS to rust-analyzer, was worth it for me