For the next major version, would it be a good idea to "flatten" rust-geo's public API? The way I see it, you only want access to the datatypes and the traits used to manipulate them. Therefore you could alter things so that the only things exported are the prelude module and types::*.

We'd still leave the algorithms module as it is on disk because the way it is currently structured allows nice separation between components. This would just rearrange how things are viewed by the user.

I'm imagining a top level lib.rs which looks like this:

mod traits;
mod types;
mod algorithm;

// re-exports to provide a more flattened API
pub use types::*;
pub mod prelude {
  ...
}

What are people's thoughts? This would technically be a breaking change (therefore you'd need to bump the major version) because people will have code which does use geo::algorithm::distance::Distance, but I feel like restructuring the public API like this will make it much flatter and simpler to deal with.

bors r+

thanks! opened a new issue for flattening the API: #163

Build succeeded

• continuous-integration/travis-ci/push