Re: PATCH: Fully Resumable VM (yield across pcall/callback/meta/iter)

[Ben Sunshine-Hill <sneftel@...>]

Apologies if I'm missing something obvious, but under this patch, what
features are in place to prevent resource leaks with a C function that
allows yielding after having locked a resource, and then is never
resumed (thread is GCed)? Obviously, one could stick a userdata on the
stack with a custom __gc for cleanup, but is there a less roundabout
way?

Ben