4 ms·
Hi author here, I won't lie, it's rough. I definitely built this whole website and wrote the blog during my "compile breaks". On the bright side, typechecking i
by djrenren 8y ago
Hi author here, I won't lie, it's rough. I definitely built this whole website and wrote the blog during my "compile breaks". On the bright side, typechecking is super fast so I only really have to wait when making algorithmic changes. Still, especially for anything that does code generation, you'll be tweaking the algorithm a good deal.
- antpls 8y agoWould building the compiler on cloud instances help? If the compiler is built in Rust, I guess it would efficiently use several dozens of cores and gigabytes of RAM
- hinkley 8y agoThere's a cargo watch command that tries to do the same thing that other languages with slow compilation or test frameworks do, and that's to run all your tests the minute you save. This narrows the time between when you have something to test and when you remember to test it. It saves you wall clock time if not CPU time. (I highly recommend combining watch with an editor or IDE that saves all buffers at the same time, instead of one at a time).
- djrenren 8y agoI don't believe this would work with the rustc compiler because, although it uses Cargo to build, it has a special process that bootstraps the compiler by building itself.