![]() Here's the output: A run of cargo-timingsĪccording to the Rust 2019 survey, improving compile times is #4 on the Rust wishlist: Rust Survey results 2019. This will generate a report on how much time was spent on each step involved in compiling your program. If you like to know what's slowing down your builds, run cargo build -timings That said, above a certain project size, the compile times are. In general, comparing across different programming languages makes little sense and overall, the Rust compiler is legitimately doing a great job. This has advantages (more flexibility when tweaking the entire compilation process, yay) and disadvantages (higher overall maintenance cost and fewer supported architectures). On top of that, the Go compiler was built from scratch as a monolithic toolchain consisting of both, the frontend and the backend (rather than relying on, say, LLVM to take over the backend part, which is the case for Rust or Swift). For example, it lacks support for generics and macros. Wait a sec, slow in comparison to what? That is, if you compare Rust with Go, the Go compiler is doing a lot less work in general.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |