Daniel P. Clark

Alright the Rust `eval` method for the Ruby API will return a `Result` allowing us to work with exceptions perfectly between Ruby and Rust. An example is provided.

Alright, I figured out how to use `rb_scan_args` in Rust. It's pretty simple. You give it a mapping of how the parameters will be laid out as a string and...

Excerpt from [The Definitive Guide to Ruby's C API](http://silverhammermba.github.io/emberb/c/) for the string mapping: ### Parsing Arguments Well, if you accept a variable number of arguments you could code all of...

I have working splat code now in my master branch of FasterPath, although it's just for one method. You can see it here: https://github.com/danielpclark/faster_path/blob/v0.2.5/src/pathname_sys.rs#L23-L36

Just to be clear you'll still have support for this? *I'm starting to port my project from FFI to ruru and my project is most useful with Rails 3 &...

> Perhaps in Rust land, every Ruby method should return a `Result` instead of simply `T`? I'm in favor of this. I think `Exception` can be a simple alias to...

@coder543 If you'd like — I've made an official fork of this project called [Rutie](https://github.com/danielpclark/rutie/). It has this feature merged in as well as all of my other PRs. Notes...

Rutie now has `RString::from_bytes` as well.

Thanks, I don't need help, and yes we're waiting for `ruby-sys`. In the mean time I've got all my PRs here available to use from the `playground` branch of my...

I think having the Rust way is preferable. We can manage the context of ownership like we normally would in Rust. We can let each language behave in their own...