4 ms·
> How does your workflow (when writing/reading code) actually look day-to-day? If you're writing a web server, are you really stopping the server, compiling aga
by ianpurton 5y ago
> How does your workflow (when writing/reading code) actually look day-to-day? If you're writing a web server, are you really stopping the server, compiling again, run the full server when doing changes the logic for the server?
You can run cargo watch which will see file changes and then stop the server, compile and then re-start it for you.
For incremental changes you're looking at about 2-10 seconds of delay depending on the complexity of the framework in use. i.e. Axum is faster than Actix.
Before you get to that state you're probably in vscode with rust analyzer, this will point out any compiler errors earlier in the lifecycle.
The rust compiler does a lot. It's catching issues before they get to production.
I'm hoping that maybe the m1 pro/max chips can get my incremental compilations to sub 1 seconds and then I get a fast workflow with the full rust compiler safety net.