Some observations on bloat in Rust and how to push back:https://raphlinus.github.io/rust/2019/08/21/rust-bloat.html …
-
-
Replying to @raphlinus
Hey! Do you have reference: re slow compilation of async code? The blog post you linked is about runtime/generated-code-size rather than compile time. It's not clear to me why async (especially if you used a trivial executor rather than tokio) would be slower to compile.
1 reply 0 retweets 0 likes -
Replying to @stuhood
Unfortunately I don't have hard numbers. I think if there are problems with code size, compile time will also be bad. I would expect combinator-based Futures to be slower just because the types are so much bigger. Worth exploring quantitatively...
1 reply 0 retweets 1 like -
Replying to @raphlinus
Agreed re: combinator based. Use of generators to implement async in the compiler will (hopefully) mostly eliminate combinators. I wouldn't be surprised though if compiler performance had been deprioritized a bit in the rush to stabilize async/await: just haven't seen examples.
1 reply 0 retweets 0 likes
It would be *awesome* if compile time / code size for async code were competitive with sync. I guess we'll have to see how it settles out, after people get a chance to measure and tune.
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.