Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
This PR updates the
hashCode
implementation for theLatLng
class to use the XOR strategy. This approach aims to reduce hash code collisions by providing a better distribution of hash codes compared to simple addition.Changes:
Updated the hashCode method in the
LatLng
class to use XOR (latitude.hashCode ^ longitude.hashCode
).Benefits:
Reduced hash code collisions, leading to more efficient use of hash maps and sets.
Improved overall performance in collections that rely on hash codes.
Collision Example:
With the previous implementation using addition, the following pairs of coordinates produce the same hash code:
(latitude: 1.0, longitude: 2.0)
(latitude: 2.0, longitude: 1.0)
Both pairs will produce the same hash code since
1.hashCode + 2.hashCode == 2.hashCode + 1.hashCode
.By using the XOR strategy, these pairs will generate different hash codes, reducing the likelihood of collisions.