4 ms·
Is it just me or you're supporting your parent's point of: > ...the decision was effectively made on the ground of "we want to ship async support as soon as po
by hu3 6y ago
Is it just me or you're supporting your parent's point of:
> ...the decision was effectively made on the ground of "we want to ship async support as soon as possible" [1].
When you write:
> Moreover, getting a usable async/await MVP was absolutely essential to getting Rust the escape velocity to survive the ejection from Mozilla...
This whole situation saddens me. I wish Mozilla could have given you guys more breathing room to work on such critical parts. Regardless, thank you for your dedication.
- withoutboats2 6y agoThat is not a correct reading of the situation. async/await was not rushed, and does not have flaws that could have been solved with more time. async/await will continue to improve in a backward compatible way, as it already has since it was released in 2019.