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.
-
Prikaži ovu nit
-
(2) There’s no high-profile language design decision you can point to and say “aha, that was a mistake!” No header files, for example. The slowness comes from a lot of smaller things that have real benefits, such as the borrow check.
9 replies 5 proslijeđenih tweetova 93 korisnika označavaju da im se sviđaPrikaži ovu nit
Odgovor korisniku/ci @pcwalton
I think there are some clear unforced errors like name resolution (though these matter more for IDE responsiveness than batch throughput)
11:25 - 2. velj 2020.
0 replies
0 proslijeđenih tweetova
4 korisnika označavaju da im se sviđa
Č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.