"Usually" is a funny word, but I see what you are saying. I guess if you are in a single-threaded event loop scenario (ala nodejs) you could get away with it s

"Usually" is a funny word, but I see what you are saying. I guess if you are in a single-threaded event loop scenario (ala nodejs) you could get away with it somewhat, but as soon as you introduced multiple threads of execution all bets are off. That's unfortunate. We have a fairly large codebase written in .NET. We wouldn't mind porting it to CoreCLR, but we'd have to migrate everything to async/await. The red/blue nature of method signatures makes this look like almost a complete rewrite. Given the difficulty of this migration so far, and the nature of the change, it's certainly caused us to explore other options and we've already rewritten a significant chunk of the code in Go. Moving a large codebase from a single color model to a dual color model really sucks. I hope Rust can lock this down sooner rather than later otherwise a lot of people are going to feel pain down the road. The good news is you have a good static type system. I cannot even begin to imagine migrating a Python codebase to async/await...