-
Notifications
You must be signed in to change notification settings - Fork 933
fix: Add parenthesis around ..
closure if it's a method call receiver
#5842
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
trait Trait { | ||
fn method(&self) {} | ||
} | ||
|
||
impl<F: Fn() -> T, T> Trait for F {} | ||
|
||
impl Trait for f32 {} | ||
|
||
fn main() { | ||
|| 10. .method(); | ||
|| .. .method(); | ||
|| 1.. .method(); | ||
} |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
trait Trait { | ||
fn method(&self) {} | ||
} | ||
|
||
impl<F: Fn() -> T, T> Trait for F {} | ||
|
||
impl Trait for f32 {} | ||
|
||
fn main() { | ||
|| (10.).method(); | ||
(|| ..).method(); | ||
(|| 1..).method(); | ||
} |
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 was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are the parens being applied in the correct place in the first example? Shouldn't it be
(|| 10.).method();
if we're applying the method to the closure?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should be correct iirc. This is just one of the weird precedence things
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just checked and here are the ASTs that rustfmt sees when parsing
AST wrapping float in parens
AST wrapping closure in parens
And here's the diff when comparing wrapping the float vs wrapping the closure. For reference I saved both ASTs to files and ran
git --no-pager diff --no-index wrap_float_with_parens_ast.txt wrap_closure_with_parens_ast.txt
From the AST level it seems that the first is treated as a closure that contains a method call, while the second is a method call on a tuple.
AST Diff
If there are compilation steps that happen after parsing that ensures that
|| (10.).method();
means "apply the method call to the return value of the closure then I think we're good to go, otherwise I'd like to change the output to produce(|| 10.).method();
for consistency, and because I think that(|| 10.).method();
more clearly conveys that we're applying the method to the returned value of the closure.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe we aren't applying it to the closure in specific, but the float, yet for some reason the previous
lit_ends_in_dot
check didn't apply here.Changing it to
(|| 10.).method()
applies it to the closure as you noticed, which does cause differing behavior (and can cause compile errors if the trait isn't implemented for closures, which isn't good)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I just double checked and it turns out that the code highlighted in the first example of #5842 (comment) (inlined below for reference)
parses as a closure and the the method is applied to the
10.
while the second example from that comment (inlined below for reference) parses as method call where the receiver is a closure.