Just disable additional cargo check after save and/or after any change.
waiting for rust-analyzer
Submitted 10 months ago by Xylight@lemmy.xylight.dev to programmer_humor@programming.dev
https://backend.xylight.dev/api/files/l4rgemtdlgd37rz/banjiii8kgqrlnc/cargo_vibe_8bir8Iv7fl.mp4
Comments
fzz@programming.dev 10 months ago
Sigmatics@lemmy.ca 10 months ago
I thought Rust was fast
Zalack@startrek.website 10 months ago
Compiled Rust is fast.
Compiling Rust is slow.
Also my understanding is that RustAnalyzer has to compile all Rust macros so it can check them properly. That’s not something that a lot of static analysis tools do for things like C++ templates
LPThinker@lemmy.world 10 months ago
This is, in part, a correlation. To some extent, compiled Rust is fast because compiling Rust is slow. That is, Rust does a lot of work (static analysis) at compile time so that the runtime binary is as fast as possible.
ExperimentalGuy@programming.dev 10 months ago
I kinda love how fast the binaries are. I was timing something I wrote and, as a mostly Python dev, I was so confused when the program was running in the nanoseconds or something crazy like that and not milliseconds.
Beanie@programming.dev 10 months ago
uh I think you mean microseconds lol A nanosecond is just a few clock cycles
ExperimentalGuy@programming.dev 10 months ago
Thanks, that’s what I meant I just forgot what it was