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 microseconds or something crazy like that and not milliseconds.
this post was submitted on 03 Aug 2023
116 points (96.8% liked)
Programmer Humor
19623 readers
411 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
uh I think you mean microseconds lol
A nanosecond is just a few clock cycles
Thanks, that's what I meant I just forgot what it was
The wait is long enough for a certain Megadeth album title to become relevant.
I thought Rust was fast
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
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.
Personally I think the "compiling Rust is slow" narrative comes from comparing it against scripting languages like Python. If you compare compiling Rust against compiling C++ code of similar complexity, I think Rust will come out very favorably since C++ templates and headers tend to carry a huge compilation burden.
Just disable additional cargo check after save and/or after any change.