[phoe-krk]

I'll keep that in mind, and I'll add that link to the book's contents, and I'll add you to my book's Hall of Fame. Thanks.

[mst]

The author of Future::AsyncAwait is working on a patch to core to provide LEAVE {} blocks which will be a more full unwind-protect solution. Note of course the destructor limitation doesn't affect Worlogog use so much since you're -not- throwing exceptions, but once you're into mixed condition and exception based code of course things that to get more "fun".

[phoe-krk]

> once you're into mixed condition and exception based code of course things that to get more "fun".

I imagine that is the reality of everyone who tries to implement a condition system in a language where the default behavior is to immediately unwind the stack by throwing some sort of an exception.

[mst]

Yes. But as the only perler I've seen in this thread I wanted to do my best to be honest about the risks.

If I were to want to continue discussing this, do you happen to kick around anywhere on IRC that would be suitable?

[phoe-krk]

#lisp on Freenode sounds okay - my nickname is phoe.