You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@randallwhitman I have different fix in the full version. Note that the OGC equals is not same as java equals. Java equals is identity comparison, while OGC equals is topological.
The ogc equals is slow, and also, probably not what one expects when storing a class in a container, such a hash map. I think ogc equals it should be different from identity equals.
Activity
randallwhitman commentedon Mar 9, 2016
As mentioned in the incomplete patch, it would then also need
hashCode.stolstov commentedon Mar 9, 2016
@randallwhitman I have different fix in the full version. Note that the OGC equals is not same as java equals. Java equals is identity comparison, while OGC equals is topological.
stolstov commentedon Mar 9, 2016
Name is not good. Maybe we should rename OGC equals to Equals(OGCGeometry), and leave java equals(Object) to do Java identity thing.
randallwhitman commentedon Mar 9, 2016
In Java, operator
==is identity, whereas CustomType.equalsis conceptual equality.stolstov commentedon Mar 9, 2016
The ogc equals is slow, and also, probably not what one expects when storing a class in a container, such a hash map. I think ogc equals it should be different from identity equals.