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
Additionally equals and hashcode where they are present have incorrect Javadoc - they suggest that position and limit are not considered when comparing values, contrary to the implementation and specification. Note that this will not be reflected in generated docs (as these are emulated GWT/j2cl classes), but should be updated.
These types correctly have equals() implemented, but are missing their hashCode(), potentially leading to situations where two instances might be considered "equal" to each other, yet not have their hashcode match.
At a glance, behavior of hashcode seems unspecified, I'd be inclined to lean on the java.util.Arrays.hashCode() methods a sub-view, and some casting trickery to implement these.
The text was updated successfully, but these errors were encountered:
Additionally equals and hashcode where they are present have incorrect Javadoc - they suggest that position and limit are not considered when comparing values, contrary to the implementation and specification. Note that this will not be reflected in generated docs (as these are emulated GWT/j2cl classes), but should be updated.
These types correctly have equals() implemented, but are missing their hashCode(), potentially leading to situations where two instances might be considered "equal" to each other, yet not have their hashcode match.
At a glance, behavior of hashcode seems unspecified, I'd be inclined to lean on the
java.util.Arrays.hashCode()
methods a sub-view, and some casting trickery to implement these.The text was updated successfully, but these errors were encountered: