Add iterator for method specializations #49116
Merged
Conversation
This file contains 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
There have been longstanding reasons to want an API for extracting all extant specializations of a method, but this is even more true after #49071.
|
Since the fix in MethodAnalysis was straightforward, I thought it would be better to introduce an iterator interface, as I think more packages would find it easy to use. |
aviatesk
reviewed
Mar 23, 2023
|
I think it would be nice if |
jakobnissen
reviewed
Mar 23, 2023
Co-authored-by: Shuhei Kadowaki <[email protected]>
vtjnash
reviewed
Mar 28, 2023
Xnartharax
pushed a commit
to Xnartharax/julia
that referenced
this pull request
Apr 19, 2023
There have been longstanding reasons to want an API for extracting all extant specializations of a method, but this is even more true after JuliaLang#49071. Co-authored-by: Shuhei Kadowaki <[email protected]> Co-authored-by: Jameson Nash <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There have been longstanding reasons to want an API for extracting all extant specializations of a method, but this is even more true after #49071.