mrusty: Nested mruby Rust calls cause memory leaks in the case of uncaught exceptions.

Currently, to raise errors within Ruby from Rust, I’m using the following:

mruby
    .run("self")
    .unwrap()
    .call("raise",
           vec!(mruby.string(my_error_message)))
    .unwrap()

I noticed that there’s a method on Mruby named raise, but it’s a private method. What are the reasons behind this decision? Would it be easy to make it public, or should I continue using my current workaround?