Re:Proposal: Go 2 transition
by steveklabnik on Friday October 26, 2018 @05:37PM
(#18312892)
Futures are subject to some more change, though it’s getting close!
FWIW, async/await does produce a “stack full” coroutine: you get a single, exactly sized stack for each task, every time. This is made possible by coroutines being fundamentally stackless, but in the end, tasks still have stacks.
> FWIW, async/await does produce a “stack full” coroutine: you get a single, exactly sized stack for each task, every time. This is made possible by coroutines being fundamentally stackless, but in the end, tasks still have stacks.
I see, thanks for the info. I wasn't talking so much about the implementation but the difference between the program control flow differences between the two models, go-routines vs async/await.
Re:Proposal: Go 2 transition
by steveklabnik on Friday October 26, 2018 @06:06PM
(#18313035)
Cool cool. Both have advantages and drawbacks; I think both languages have made the right choice given their contstraints.
When I write code that is going to run on the customer’s device, I choose Rust for the guarantees it offers me, (I know it will not crash because of my mistake). For server side code on the other hand, something easy going as Go is much preferred.