Corey Farwell
Corey Farwell
Good idea. I don't think we have much of a reason to keep it around
FYI, `TryInto` is stabilized again! It's hit the latest beta, but not yet stable
https://github.com/search?l=Rust&q=togeo&type=Code
Considering there's usage of this trait in the ecosystem, I'm going to mark it as deprecated: https://github.com/georust/geo/pull/375 We can remove it in the future after some time has passed Also...
I agree with @tmcw. At least for now, I think it makes sense to leave projections out of rust-geo for now. If anyone is particularly interested in projections though, feel...
> And for that, we have the very robust proj4 library, which one fellow has already started porting into rust. BTW https://github.com/georust/rust-proj
Many of geo's core geometry types incorporate heap allocated vectors, like [`LineString`](https://docs.rs/geo/0.12.2/geo/struct.LineString.html). Do you know how we'd work around this for `no_std`?
If / when https://github.com/Stoeoef/rstar/pull/27 merges, we can move forward with this. Thanks for making this change @brenzi! We should also make sure to add a no_std entry to our CI...
If/when https://github.com/Stoeoef/rstar/pull/27 merges, we should reopen and review https://github.com/georust/geo/pull/426
As long as we have an extra job in our matrix that builds with `no_std`, and it's just adding some cfg flags, then that seems fine to me!