• ExperimentalGuy
    link
    fedilink
    arrow-up
    9
    ·
    edit-2
    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 microseconds or something crazy like that and not milliseconds.

    • Beanie
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      1 year ago

      uh I think you mean microseconds lol

      A nanosecond is just a few clock cycles

  • vettnerk@lemmy.ml
    link
    fedilink
    arrow-up
    8
    arrow-down
    1
    ·
    1 year ago

    The wait is long enough for a certain Megadeth album title to become relevant.

    • Zalack@startrek.website
      link
      fedilink
      arrow-up
      37
      ·
      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

      • Thinker@lemmy.world
        link
        fedilink
        arrow-up
        24
        ·
        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.

      • 5C5C5C
        link
        fedilink
        arrow-up
        13
        ·
        1 year ago

        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.

  • Alex
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

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