Daniel P. Clark

Have you tried an environment variable for it? `NO_LINK_RUTIE` https://github.com/danielpclark/rutie/blob/master/build.rs#L348-L351

This gem [unicode-display_width](https://github.com/janlelis/unicode-display_width) may be a possible solution, but the "marshall" data may be incompatible across Ruby versions. This Rust crate [unicode_width](https://github.com/unicode-rs/unicode-width) would work well with a Ruby gem wrapped...

The specific error I opened in Ruru that you linked to was because I use `Vec` rather than an array `[]` for method arguments sent to Ruby. The appropriate link...

@ZhangHanDong This issue is being revisited/discussed here: https://github.com/danielpclark/rutie/pull/76#issuecomment-454582628 Things may not be as we originally thought. But we need to prove it.

Thanks @kvinwang . cc @dsander

> In rutie, there are tons of Rust APIs creating Ruby objects and rely on the created objects to be put on the stack to ensure memory safety. In the...

@dsander Is it possible to reproduce the bug purely from the Rust side now that we have GC methods? We can create a `test` directory for having a unit test...

## GC/Drop Idea Just an idea. Since Ruby instantiates object's memory through the GC and cleans up objects from memory through the GC I think we could implement a `Drop`...

> I don't think this is a good idea: > * It is expensive to check if GC knows about an item. > * We are not able to prevent...

@kvinwang I'm not sure we want to avoid the heap because of this issue. I'd like to be able to use a `Vec`. If the program running is a Rust...