Remove unnecessary comparable type constraints from data structures #244
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some data structures support custom comparators. In these cases, the generic type constraint does not need to be comparable. This commit removes the unnecessary comparable type constraints from these data structures.
|
|
I also need this if I want to migrate to the v2. When can we expect a review? |
|
@emirpasic Could you please review and consider merging it soon? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Close #243.
Some data structures support custom comparators. In these cases, the generic type constraint does not need to be comparable. This PR removes the unnecessary comparable type constraints from these data structures.