Sure, any software could be better. The question is, is it useful as-is and how does it compare to other language tooling? Is it fine, or do we need to really focus on getting it up to par?

[–] [email protected] 3 points 1 week ago (1 children)

Definitely useful and I think it compares pretty well to other tooling? My two biggest issues are compile times and "amnesia". First of all, compile times because the feedback cycle can get really bad. But that's not really rust-analyzer's fault, that's cargo/rustc.

But rust-analyzer also has this weird "amnesia". Like if I have ran the checks and everything is good, I can go to definition and it will instantly bring me there. But if I make a small change and it starts running cargo check, it's like it forgets everything until it's done with cargo check. I wish it still allowed me to use what it knew before and go to definitions and give suggestions and such.

[–] [email protected] 1 points 1 week ago (1 children)

Yeah, rust-analyzer has been perfectly fine for me as well, though I honestly don't expect a ton from my editor.

weird “amnesia”

Ah, while it's processing everything again. My project is pretty small and my computer is pretty fast, so I guess I haven't noticed. I also don't use a ton of its features, because I tend to already know where things are.

[–] [email protected] 2 points 1 week ago

It's definitely not a problem in my own projects, but at work is a different story. With a huge project, compile times becomes a real slog.