Promises, continuations/coroutines, and re-entrancy (an email/some pondering to cap-talk) https://groups.google.com/forum/#!topic/cap-talk/cJwUrnzX0lk
This is related to design decisions for #Spritely Goblins.
Promises, continuations/coroutines, and re-entrancy (an email/some pondering to cap-talk) https://groups.google.com/forum/#!topic/cap-talk/cJwUrnzX0lk
This is related to design decisions for #Spritely Goblins.
Mark Miller responded usefully:
> The key is that the await or similar marking must appear at every call site. Given that explicit marking must appear anywhere interleaving may happen, and is otherwise rare, then you've taken care of the hazard.
>
> (See section 18.2 of my thesis, and the hypothetical diagonal arrow marking.)
Unfortunately this leads to a sad conclusion: building coroutines on top of delimited continuations, as I've advocated for a while, is not ocap secure on its own, as it exists in some schemes and etc. Sad.
However, with a meta-linguistic abstraction it can be tamed; unfortunately, it involves bringing back marking all coroutine'able functions with "async", which I was excited that I don't need to do.
social.giorgiocomai.eu is a social network, courtesy of Giorgio Comai. It runs on GNU social, version 1.2.0-beta4, available under the GNU Affero General Public License.
All social.giorgiocomai.eu content and data are available under the Creative Commons Attribution 3.0 license.