3 ms·
It's too bad that compiler plugins / libmacro are still so experimental. Once they're stable, the kind of code generation you're doing as a separate step could
by curun1r 11y ago
It's too bad that compiler plugins / libmacro are still so experimental. Once they're stable, the kind of code generation you're doing as a separate step could be done entirely at compile time. I did some preliminary tests with an eye towards an AWS crate, but decided that a crate that only works with nightly and frequently breaks is of dubious value. Still, it's cool that the Rust compiler will eventually be extensible enough to compile json directly.
Anyways, thanks for Rusoto. It's going to make a project I'm starting next month significantly simpler!
- Perceptes 11y agoYes, I've been following this issue closely. Nick Cameron is working on a revamped macro system that will replace the current compiler plugin system for the purposes of syntax extensions. It's probably still gonna be a while, unfortunately, since it'll take some time to get that kind of stuff vetted and baked into the language. Here are some recent posts by Nick on his experiments and progress (in order of publication): * http://www.ncameron.org/blog/macro-plans-syntax/ http://www.ncameron.org/blog/macro-plans-syntax/ * http://www.ncameron.org/blog/procedural-macros-framework/ http://www.ncameron.org/blog/procedural-macros-framework/ * http://www.ncameron.org/blog/libmacro/ http://www.ncameron.org/blog/libmacro/ Pretty much all of his recent blog posts are on the topic, so it's worth browsing through all of them if you're interested.