[ ] I added an entry to CHANGES.md if knowledge of this change could be valuable to users.
Putting this up for discussion:
Right now geo-traits only has a dependency on geo-types to
add a trait bound on T for CoordNum
add implementations of the traits on geo_types objects
As I was cleaning up https://github.com/kylebarron/wkb, I realized that geo-traits doesn't really need to have the CoordNum trait bound, because the consumer can require it separately.
What do people think about making the geo-types dep optional?
[ ] I added an entry to
CHANGES.mdif knowledge of this change could be valuable to users.Putting this up for discussion:
Right now
geo-traitsonly has a dependency ongeo-typestoTforCoordNumgeo_typesobjectsAs I was cleaning up https://github.com/kylebarron/wkb, I realized that
geo-traitsdoesn't really need to have theCoordNumtrait bound, because the consumer can require it separately.What do people think about making the
geo-typesdep optional?