Kyle Barron

I don't understand enough unsafe bits here about how you do numpy casting (I exclusively use safe APIs because I just don't understand enough about what I need to watch...

I can give feedback on using `pyo3-object_store` and on connecting async rust to python with `pyo3-async-runtimes`, but I don't think I can give any feedback on the UnsafeCellSlice

I renamed the title of this issue. I don't have strong feelings about it. I'm just used to publishing via CI in my projects because it provides an easily reproducible...

I'm not familiar with this area of the `geo` code myself, but I think you're most likely to get a helpful response if you add a reproducible example in rust,...

I don't know how to make the keyboard shortcuts from this extension override the defaults. A PR to update documentation would be welcome if you had a known fix/keyboard shortcut

I think the main question here is what the scope of `geo-traits` should be, and whether we should ship structs like this inside of `geo-traits`. As it is `geo-traits` only...

It looks like this is essentially backwards-compatible? The trait definition changes, of course, but anyone who was using this on `geo::Coord` doesn't have to change their code?

> Or—perhaps it _is_ impossible in some cases? It's not possible as you've shown because Rust doesn't have specialization. Some options: - Different algorithm trait names for impls on different...

I found it confusing because at least in a couple places, the API does do semantic handling instead of raw buffer operations. E.g. `with_capacity` reserves space for `n + 1`...

What do you think about that edit?