Every time I see another poll about the @rustlang async/await syntax, I feel like it's missing the option "I just want async/await to be stable and will defer to the Rust Core team's best judgment about the syntax"
-
Show this thread
-
mik Retweeted mik
I don't currently do any Rust programming, but thread FWIW: https://twitter.com/mik235/status/1129246179835883520 … (async/await is a mistake)
mik added,
2 replies 0 retweets 2 likes -
Promises/async/await seem like a total hack necessary for JavaScript only. Why would languages that don’t need (Rust, C++) it adopt it? What am I missing? It’s miserable in JS, too.
4 replies 0 retweets 5 likes -
Because it’s the fastest of all available options. Coroutines needs stacks and are therefore slower.
4 replies 0 retweets 6 likes -
Honestly, I'd be happy with threads and type safe queues (eg. like python's Queue). Performance is more your gig than mine, but as a programmer I can say that these are a total disaster: - async/await - Promises - Events
2 replies 0 retweets 0 likes -
I mean, I don’t disagree. I’d rather program with threads myself. As far as I’m concerned, async/await is the answer to “well, what if we want to go as fast as possible?” Then it’s about as nice as you can get without sacrificing perf.
1 reply 0 retweets 0 likes -
I guess there's stuff about how rust works that makes this performant, even when people are using closures and pretending it's all happening in the same function?
1 reply 0 retweets 0 likes
It magically all boils down to a big state machine, yep.
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.