waiting for rust-analyzer

Comments

• ExperimentalGuy@programming.dev ⁨1⁩ ⁨year⁩ 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.

  source

  • Beanie@programming.dev ⁨1⁩ ⁨year⁩ ago

    uh I think you mean microseconds lol A nanosecond is just a few clock cycles

    source

    • ExperimentalGuy@programming.dev ⁨1⁩ ⁨year⁩ ago

      Thanks, that’s what I meant I just forgot what it was

      source
• fzz@programming.dev ⁨1⁩ ⁨year⁩ ago

  Just disable additional cargo check after save and/or after any change.

  source
• Sigmatics@lemmy.ca ⁨1⁩ ⁨year⁩ ago

  I thought Rust was fast

  source

  • Zalack@startrek.website ⁨1⁩ ⁨year⁩ 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

    source

    • LPThinker@lemmy.world ⁨1⁩ ⁨year⁩ 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.

      source