Simplify minimum/maximum on sparse vectors #42845
Merged
+3
−9
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.
I couldn't detect an ambiguity, and also this didn't avoid ambiguities. If there was one, it would still exist for callable objects of type different then
Function
orType
.@alyst Do you remember what type of ambiguity you found back then? It could be that by the time #29884 got merged (2.5 years after first commit), the ambiguity was already resolved.