Allow opting out of PartialOpaque support via Expr(:opaque_closure, ...)
#55068
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
Member
|
I think at that point you might be beyond |
Member
Author
Do you mean generating the IR for the closure by hand? |
Member
|
Member
Author
|
Oh, you mean keeping the lowering changes but not changing the macro - yeah, that's fine by me |
Member
|
Yes |
topolarity
force-pushed
the
ct/opaque-closure-nopartial
branch
2 times, most recently
from
0773dab to
ad99efe
Compare
topolarity
changed the title
PartialOpaque support via @opaquePartialOpaque support via Expr(:opaque_closure, ...)
Member
Author
|
@Keno OK to merge? |
KristofferC
pushed a commit
that referenced
this pull request
Sep 12, 2024
…, ...)` (#55068) This can be useful for when an OpaqueClosure is desired, e.g., as an invalidation barrier or when you know it passes through an inference barrier naturally (in my case, a mutable type). This is intentionally left undocumented for now.
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.
This can be useful for when an OpaqueClosure is desired, e.g., as an invalidation barrier or when you know it passes through an inference barrier naturally (in my case, a mutable type).
This is intentionally left undocumented for now.