Resolve ambiguity of .IndexOfOrNone extension method
#855
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
FreeApophis
approved these changes
Mar 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Currently using
IndexOfOrNoneon a concrete immutable collection such asImmutableArrayorImmutableListresults in an ambiguous overload error.This was not directly fixable using
[OverloadResolutionPriority]since the conflicting extension methods are in two different classes.I moved the immutable list overloads to
ListExtensionsbut kept the old methods around to avoid a binary breaking change. I only removed thethismodifier (which is not a binary breaking change, see #346)This PR is probably best reviewed on a per-commit basis :)