3 ms·
What i would hope for is implicit async/await so i don't have to write it out / wrap all the time
by ikekkdcjkfke 3y ago
What i would hope for is implicit async/await so i don't have to write it out / wrap all the time
- groestl 3y agoThat's eerily similar to what (green) threads are.
- hinkley 3y agoI’ve always thought async await is just a less clunky implementation of green threads. Not as a feature parity replacement, but trying to fill the same niche.
- yodon 3y ago>implicit async/await I keep suspecting C# will be the place where we see this, but probably not for another couple years.
- asabla 3y agoWe might not be that far away already. There is this issue[1] on Github, where Microsoft and the community discuss some significant changes. There is still a lot of questions unanswered, but initial tests look promising. Ref: https://github.com/dotnet/runtime/issues/94620 https://github.com/dotnet/runtime/issues/94620
- anonymoushn 3y agoWe have it in Zig, Lua, Python, C, etc.
- t-writescode 3y agoIn Kotlin, only the outer-most wrapping 'suspend' function swap needs to be wrapped; and when you're writing web servers and such, that's handled in the server middleware and so all your code can be `suspend fun blahblah()`
- Aardwolf 3y agoYeah, fully agree with that. To me this is akin to writing line numbers in old BASIC dialects. The language makes the user do something that ought to be automated.