Rust compiler performance is hard to have meaningful discussions about because: (1) There’s no single part of the compiler which is slow. In fact the compiler is pretty well optimized.
-
-
Or compile to a program, then check (delayed check).
-
I mean, that the compiler first dumps a maybe-working but unoptimized binary, and only then reports borrow breakage. Probably defeats the purpose of Rust though. And maybe people would do hacky deployments using this mode

- Još 3 druga odgovora
Novi razgovor -
-
-
Seems you'd always want no-check when building as a user rather than a developer unless you distrust upstream...
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
That very much depends on your code. Rust's type system for example is very powerful, but actually using that power will cost compile time.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Splitting your code in smaller crates with less dependencies will make the compilation process quicker. Usually a big monolith project in where you compile everything every time is the wrong decision there.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.