Good point - I didn't see that additional semantic to your PR. No harm in having such a method. Not sure about the naming, though.
On Sat, Nov 28, 2020 at 7:00 PM Daniel Baston <dbas...@gmail.com> wrote: > Of all the design decisions made in the white heat of the development of >> the initial release of JTS, the ordering of arguments to the Envelope >> constructor is one I regret most. Don't see a way to change it now though >> (ideas welcome). >> > > I've been thinking of an alternate way to construct an envelope when you > know which of your inputs is the min. Currently GEOS assumes they're > unordered and checks which x value is the min and which is the max, so > there is a tiny optimization potential here. We could kill two birds with > one stone and "fix" the ordering: > > https://github.com/libgeos/geos/pull/356 > > Dan > > > > > _______________________________________________ > geos-devel mailing list > geos-devel@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/geos-devel >
_______________________________________________ geos-devel mailing list geos-devel@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/geos-devel
