i.e. at least means I've thought through stuff like "who owns this reference and should be responsible for freeing it"
borrowing is an important trick in rust and very easy to mess up.
-
-
even when I have multiple pointers, I've a clear idea of who should clean them up
-
the hardest thing so far is the control flow around yielding to user code and how that failing might break your memory management
-
you'll need a generous helping of rb_protect
-
ooh nice
-
does the `body` function take a single ruby-array VALUE (http://phrogz.net/programmingruby/ext_ruby.html … is not clear)
-
The signature there suuuucks. Basically the function is called with args passed directly, so you can have it be whatever.
-
yeah. My plan for helix is to use rb_protect around the call sites, then panic up to the FFI boundary.
-
then re-raise. That way normal unwinding takes care of normal cleanup.
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.