-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
fix #44328: method validation for opaque closures #44335
Merged
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
simeonschaub
added
backport 1.8
Change should be backported to release-1.8
bugfix
This change fixes an existing bug
labels
Feb 24, 2022
I believe it's intentional that for these methods, the `sig` field is just ignored and always set to `Tuple`. Also fixes a lowering bug I discovered that would cause errors if `Union` was shadowed. I have verified that this fixes the reported warnings.
simeonschaub
force-pushed
the
sds/fix_44328
branch
from
February 24, 2022 22:34
5cf441b
to
cff47d5
Compare
Just to check my understanding, you're suggesting it's a spurious warning? |
Yes, exactly |
47 tasks
vtjnash
reviewed
Feb 25, 2022
staticfloat
pushed a commit
to JuliaCI/julia-buildkite-testing
that referenced
this pull request
Mar 2, 2022
…#44335) I believe it's intentional that for these methods, the `sig` field is just ignored and always set to `Tuple`. Also fixes a lowering bug I discovered that would cause errors if `Union` was shadowed. I have verified that this fixes the reported warnings. Co-authored-by: Jameson Nash <vtjnash@gmail.com>
DilumAluthge
removed
the
merge me
PR is reviewed. Merge when all tests are passing
label
Mar 3, 2022
KristofferC
pushed a commit
that referenced
this pull request
Mar 3, 2022
I believe it's intentional that for these methods, the `sig` field is just ignored and always set to `Tuple`. Also fixes a lowering bug I discovered that would cause errors if `Union` was shadowed. I have verified that this fixes the reported warnings. Co-authored-by: Jameson Nash <vtjnash@gmail.com> (cherry picked from commit 5deb503)
KristofferC
pushed a commit
that referenced
this pull request
Mar 7, 2022
I believe it's intentional that for these methods, the `sig` field is just ignored and always set to `Tuple`. Also fixes a lowering bug I discovered that would cause errors if `Union` was shadowed. I have verified that this fixes the reported warnings. Co-authored-by: Jameson Nash <vtjnash@gmail.com> (cherry picked from commit 5deb503)
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.
I believe it's intentional that for these methods, the
sig
field isjust ignored and always set to
Tuple
. Also fixes a lowering bug Idiscovered that would cause errors if
Union
was shadowed.I have verified that this fixes the reported warnings.