Theoretically, yes. In practice, people are just copying Python mistakes word-for-word, in an attempt to score the "coolness" factor that async garnered in the Python community. (Never mind that the "coolness" came from solving a problem that doesn't even exist in other languages...)
If you want to see what asynchronous programming would look like if it weren't copied from Python, look at the recent C++ proposal.
> - If you don't need it, don't use it. Rust without asynchronous functions still looks and works like before
The problem is that every Python library now comes in two versions, regular and 'async'. Even if you don't need or care about anything 'async'.
I guess splintering your code base into two incompatible flavors is just the pythonic way of doing things? Now that the 2 vs 3 insanity is finally dying down, they needed to start a fresh one?
Why is Rust trying hard to repeat these mistakes?
> - By the way: welcome to C++20's coroutines
That I already answered above.
- Asynchronous programming is completely orthogonal to Python
- If you don't need it, don't use it. Rust without asynchronous functions still looks and works like before
- By the way: welcome to C++20's coroutines