> Build times

> I'm surprised I didn't see any advice about skipping proc macros or Serde for faster compile times.

A more comprehensive document on build times is at https://corrode.dev/blog/tips-for-faster-rust-compile-times/

We're integrating parts of it into Cargo's official documentation at https://doc.rust-lang.org/nightly/cargo/guide/build-performa...

We're coordinating the work on that at https://github.com/rust-lang/cargo/issues/16119

> > If you use dev builds but don’t often use a debugger, consider disabling debuginfo. This can improve dev build times significantly, by as much as 20-40%.

We're wondering if we should split iterative development from debugging to pull in these improvements (and maybe more). This is being explored at https://github.com/rust-lang/cargo/issues/15931

Any chance we could get macros that do physical-code-on-machine codegen? (Like Google protobuf?)

I love Serde to death, but the compile times are getting absolutely absurd. It's painful to sit around for three minutes after a single code change.

If I could use Serde with all of its features, but have it write out the source to disk so I can commit it to our repo, that seems like it would vastly improve compile times. During development, I'd love to be able to change our API definition and be able to rapidly test changes. The productivity loss with the current state of Serde and proc macros sucks.

Any chance of something like that happening? I'd use it in a heartbeat. I would donate to fund this.