so figuring out who "owns" what and what state everything is in *before* yielding to user code is crucial and easily broken
rust would do all that, but just as a natural consequence of ownership semantics.
-
-
curious: what does "might not return" mean?
-
it yields to ruby via rb_funcall, which ends up invoking user-supplied callbacks that might unwind the stack
-
unwind or longjmp?
-
I'm not sure at that level, I mean "might raise or return"
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.