Dmitry Gritsay
Dmitry Gritsay
The following methods should take `self` by value, because technically they return the same Ruby objects converted to another Rust type. - [ ] `Object::to` ```rust Object::to(&self) -> T ```...
```rust handle_exceptions! { begin { // ... } rescue TypeError => e { // ... } rescue ArgumentError => e { // ... } rescue => e { // StandardError...
Change `class!`, `methods!` and `unsafe_methods!` macro to have a better API for defining Ruby classes (needs discussion and decision).
- [ ] `rb_rescue` - [ ] `rb_ensure` - [ ] `rb_jump_tag` ?
Consider the following example: ```rust let string = RString::new("Some string"); let mut array = Array::new(); // Moves `string` into `array` similarly to `vec.push()` in Rust array.push(string); // ... `string` cannot...
`RbConfig::CONFIG` provides all the required information for linking with static libraries. But Cargo does not allow to use all the flags, for example `-framework CoreFoundation` on Mac OS X. Investigate...
Mark `Fixnum` struct as deprecated to have a consistent API with 2.4.
Add basic support for `Module`s. Also there may be some common functionality which is implemented in `Class` struct. Extract the logic to a trait in this case.
Implement `Copy` trait similarly to Rust primitive types. Should be implemented for those types which have constant `object_id`s. - [ ] `Boolean` - [ ] `Float` - [ ] `Integer`...