magnus VS polars-ruby

You can also use Rust to write an extension module that can be loaded into the Ruby interpreter, so that everything runs in the same process: https://github.com/matsadler/magnus

So while the Arrow C binding for the Ruby language is relatively well-developed, polars-df is not an Arrow C binding, but a binding to Polars implemented in Rust. magnus is used for the connection between Ruby and Rust. In fact, there is also a Ruby data frame that uses the Arrow binding, which is called RedAmber. But we are not talking about that now.

The template generated with bundle gem —-ext=rust uses the Magnus[1] library that provides a high-level friendly Rust wrapper over the Ruby C API, but you can also use rb-sys[2] which is lower level bindings direct to the Ruby C API.

[1]: https://github.com/matsadler/magnus

You might give this https://github.com/ankane/polars-ruby a look.

polars-df

https://github.com/ankane/polars-ruby is an example that was just posted here recently

Polars is a data frame in the Rust language using Apache Arrow Columnar Format. polars-ruby is the Ruby binding for Polars created by Andrew Kane.

I think its really interesting such gems offering a layer ruby on top of rust libs. One issue that I have with that is - and maybe it's my ignorance - but is that necessary to bundle the original lib as https://github.com/ankane/polars-ruby/tree/master/ext/polars ? I can imagine that makes easier to avoid breakage but couldn't we at least lock its version in Cargo.toml?