Writing macro_rules macros by hand really does give me the "programming is writing weird gibberish"-feel.
-
Show this thread
-
Replying to @yoshuawuyts
Right? I think that's why I avoided it for so long
1 reply 0 retweets 2 likes -
Replying to @jntrnr
I'm super stoked for all the proc macro goodness folks have been talking about. Heard folks are now experimenting with pre-compiling proc macros to wasm so we can get rid of the syn + quote compilation from http://crates.io , which would make all of this so much better!! :D
2 replies 2 retweets 9 likes -
Replying to @yoshuawuyts
I hadn't heard about that, but it sounds awesome2 replies 0 retweets 3 likes -
Replying to @jntrnr
Haha yeah
@davidtolnay told me agput it during RustConf, and so excited about it also!!!1 reply 0 retweets 3 likes -
I'm extremely confused at how wasm affects proc macros
1 reply 0 retweets 4 likes -
We'd like to have http://crates.io distribute proc macros as precompiled wasm binaries that are executed by a wasm runtime in the compiler. Then adding a dependency on a proc macro no longer adds anything to compile time.
4 replies 6 retweets 26 likes -
Replying to @davidtolnay @sgrif and
I assumed http://crates.io would distribute precompiled native binaries for a few popular combinations of (rustc version, target). WASM solves proc macros, but proc macros are just a small fraction of all deps.
1 reply 0 retweets 0 likes
It's been discussed, there's a lot more work for cargo to support that than us
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.