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.
-
-
-
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...
- 2 more replies
New conversation -
-
-
Great blog post! Btw, does cargo bloat also report the contribution to compilation time by each dep? If not, is there a way to get this from cargo? So far I've mostly been eyeballing it by seeing what cargo build gets stuck on
-
Excellent question, as this is perhaps not widely known. Yes, `cargo bloat --time` will report compilation time contribution as well.
- 1 more reply
New conversation -
-
-
Tokio has a goal of reducing the dep weight: https://github.com/tokio-rs/tokio/issues/1391 …. Dependencies are combined, functionality made optional or opt-in. There is a limit to what we can do though. If you have specific thoughts for Tokio, I would be happy to dig in.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thank you for the great post! I’d love to see improvements in this area too. This ticket has been waiting in my todo list for a long whilehttps://github.com/rust-lang-nursery/rustc-perf/issues/145#issuecomment-499298004 …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I have found that MessagePack serialisation is both faster and produces smaller code. I use rmp-serde for storing state between restarts in XV.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Indeed bloat is a great problem to Rust. Especially useless crates like failure and stuff like that, yet people think it is fine to use unnecessary dependencies
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.