Permit the || syntax to be used for both boxed and unboxed closures
#19113
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
…h the fulfillment contect if necessary.
…h an optional unboxed closure kind.
nikomatsakis
force-pushed
the
unboxed-boxed-closure-unification
branch
from
175c0d1 to
b9c5cd4
Compare
This was referenced Nov 20, 2014
Closed
|
Giving this high priority because of the importance of unboxed closures for 1.0. |
bors
added a commit
that referenced
this pull request
Nov 20, 2014
…ation, r=acrichto Use the expected type to infer the argument/return types of unboxed closures. Also, in `||` expressions, use the expected type to decide if the result should be a boxed or unboxed closure (and if an unboxed closure, what kind). This supercedes PR #19089, which was already reviewed by @pcwalton.
lnicola
added a commit
to lnicola/rust
that referenced
this pull request
Feb 10, 2025
Update PRIVACY.md
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Use the expected type to infer the argument/return types of unboxed closures. Also, in
||expressions, use the expected type to decide if the result should be a boxed or unboxed closure (and if an unboxed closure, what kind).This supercedes PR #19089, which was already reviewed by @pcwalton.