Corey Farwell

index out of bounds panic when parsing bytes

1

```rust extern crate flac; use flac::{ByteStream, Stream}; fn main() { let s = Stream::::from_buffer(b"fLaC\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00H\x01\x00\x00\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\xff\xff\xff\xff\\"); if let Ok(mut stream) = s { let _ = stream.info(); let _ = stream.metadata(); let...

[returns a 404](https://camo.githubusercontent.com/21d7afbbbad6d4798e3dea26b5234dc10e0f0dfe/687474703a2f2f646f6d65737469636361742e636f6d2e61752f70726f6a656374732f696e74726f73706563742f696e74726f737065637464656d6f2e706e67)

There are operations within these algorithms that can panic. We should update these algorithms to be panic-free, and instead return `Result`s. An attempt was made in https://github.com/georust/geo/pull/589

Remove the `approx` feature requirement for `geo-types` in the `geo` crate?

1

Do we need this? https://github.com/georust/geo/blob/a3c2094990f87ac9e31420893bd2c1a0e43711e8/geo/Cargo.toml#L19 Could it just be a feature we enable in tests?

Add it here: https://github.com/georust/geo/blob/1d3b32970a49746de6ce2400305725edd21f7c15/geo/src/lib.rs#L124-L130

Implement `HaversineDistance` for all combinations of geometry types

18

Right now it's only implemented between two `Point`s https://docs.rs/geo/0.20.1/geo/algorithm/haversine_distance/trait.HaversineDistance.html

- [ ] I agree to follow the project's [code of conduct](https://github.com/georust/geo/blob/main/CODE_OF_CONDUCT.md). - [ ] I added an entry to `CHANGES.md` if knowledge of this change could be valuable to...