the first thing you learn when writing rust is how less rigorous you were than you thought.
-
-
Replying to @wycats
I'm trying to arrange things so there's usually only one pointer to something in existence, which is tricky
2 replies 0 retweets 0 likes -
Replying to @mountain_ghosts
borrowing is an important trick in rust and very easy to mess up.
1 reply 0 retweets 0 likes -
Replying to @wycats
even when I have multiple pointers, I've a clear idea of who should clean them up
1 reply 0 retweets 0 likes -
Replying to @mountain_ghosts @wycats
the hardest thing so far is the control flow around yielding to user code and how that failing might break your memory management
2 replies 0 retweets 1 like -
Replying to @mountain_ghosts @wycats
you'll need a generous helping of rb_protect
1 reply 0 retweets 0 likes -
ooh nice
1 reply 0 retweets 0 likes -
Replying to @mountain_ghosts @evanphx
does the `body` function take a single ruby-array VALUE (http://phrogz.net/programmingruby/ext_ruby.html … is not clear)
2 replies 0 retweets 0 likes -
Replying to @mountain_ghosts
The signature there suuuucks. Basically the function is called with args passed directly, so you can have it be whatever.
1 reply 0 retweets 0 likes -
Replying to @evanphx @mountain_ghosts
yeah. My plan for helix is to use rb_protect around the call sites, then panic up to the FFI boundary.
2 replies 0 retweets 0 likes
then re-raise. That way normal unwinding takes care of normal cleanup.
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.