Why stackless (async/await) for Swift?

[dabrahams (Dave Abrahams)]

@Joe_Groff

We'll hopefully eventually have reasync , akin to rethrows…

It's a start. I think we probably need something like reasync at a protocol granularity, so that the async-ness of my BundleOfCallbacks instance can determine the async-ness of the algorithm using that bundle. But we'll still be left with a lot of meaningless syntax overhead.

@tera

update to update: you can do your own "fiber testing" without fibers: just malloc a bunch (say a million) of megabyte sized blocks (one malloc per each block or one giant malloc for all blocks) and write the first 1K in each block. i won't be surprised if half of current popular platforms/devices fail this test.

Sure, but as noted by the Boost.Fiber people, it's a fallacy that you need to allocate 1M for fiber stacks, in general. There are lots of interesting points in the design space.