Change IComparer interface argument so that it accepts nulls. #89
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.
Currently
ISemVersionComparer
and its concrete implementations implementsIComparer<SemVersion>
which forces one to use the bang operator when using it with some apis like the Linq Order APIs.Current usage example:
To get rid of the warning, one has to use the !bang operator to make the compiler happy like so:
.OrderByDescending(x => x, SemVersion.PrecedenceComparer!);
However, I think this is unncessary as the implementation rightly supports nullable comparison.
With this change, the nullability is also documented on the exposing interface to make usage in some APIS easier without any warnings.