Kyle Barron

I think we should keep anything on `GeometryArrayTrait` that has high general functionality while still allowing the trait to be object safe. Therefore, I feel strongly that `into_array_ref` should exist...

I'm not certain whether I still want this as a goal, or whether at some point in the future it would be better to move python, js, etc bindings into...

also typedoc namespacing: https://github.com/Gerrit0/typedoc-packages-example/blob/master/packages/bar/typedoc.json

some docs on conda wheels: https://github.com/ocefpaf/netcdf4-win-wheels

- don't use C as the generic name as that overlaps with the name georust/geo gives to the numeric type pseudocode from my phone: ```rs trait Coord { } trait...

Solved in https://github.com/geoarrow/geoarrow-rs/pull/661 as part of https://github.com/geoarrow/geoarrow-rs/issues/662

> I'd also like to contribute but I don't know Rust so there's that... I'm happy to provide tips and point you to easy first PRs if Rust is something...

I made stubs at https://github.com/kylebarron/geoarrow-rs/issues/104 and https://github.com/kylebarron/geoarrow-rs/issues/105, where we can discuss good first issues. I haven't given much thought yet to what are some simpler tasks that are good for...

We also need to figure out some way to test that this is actually calling the release callback and that the referenced memory is actually deallocated.

You should be able to check that the release callback is now null https://arrow.apache.org/docs/format/CDataInterface.html#released-structure