Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simplify minimum/maximum on sparse vectors #42845

Merged
merged 1 commit into from
Nov 2, 2021
Merged

Conversation

dkarrasch
Copy link
Member

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 or Type.

@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.

@alyst
Copy link
Contributor

alyst commented Oct 29, 2021

Unfortunately, I don't recall the details.
I guess it was ambiguity in maximum(f, x::AbstractSparseVector) vs maximum(f::Union{Function, Type}, x), something like this.

@KristofferC
Copy link
Member

Is there a need to backport this (does it fix something)? Otherwise, it might as well just be on master?

@dkarrasch
Copy link
Member Author

Is there a need to backport this (does it fix something)? Otherwise, it might as well just be on master?

Well, it "beautifies" something that was added in the v1.7 cycle. Perhaps not necessary.

@dkarrasch dkarrasch merged commit 2179795 into master Nov 2, 2021
@dkarrasch dkarrasch deleted the dk/simplifysparseminmax branch November 2, 2021 10:17
LilithHafner pushed a commit to LilithHafner/julia that referenced this pull request Feb 22, 2022
LilithHafner pushed a commit to LilithHafner/julia that referenced this pull request Mar 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants