Re:Rust can be difficult to learn and frustrating, but it's ...
by ammaskartik on Monday October 22, 2018 @06:19PM
(#18279062)
While compile times can be slow, the rust system is checking so much for you, so that you can have a predictable @scale runtime. What was the issue with tokio?
Plus, with async/await Futures coming in soon, already on nightly right, this should become good if not already?
Rust went down the Kotlin route of not including coroutines/async/await initially and allowed Lib devs to build, but now have included as we all know. But anyways, keep at it, I have found Rust to be very helpful, using it at the startup I am at, and will keep using it deeper and in more complex scenarios.
[ Parent
| on HN ]
Re:Rust can be difficult to learn and frustrating, but it's ...
by nicoburns on Sunday October 28, 2018 @09:33PM
(#18324330)
Rust is checking a lot, but type checking is not the slow part! (I can usually run cargo check within a couple of seconds max). Rusts LLVM IR output, LLVM, and linking seem to be the main culprits. And I'm hopeful that these can be greatly improved :)