-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Suggest use "{}", self.x instead of {self.x} when resolve x as field of self
#141213
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
Show all changes
4 commits
Select commit
Hold shift + click to select a range
fe0663c
Add test sugg-field-in-format-string-issue-141136
xizheyin 9de7fff
Suggest use `"{}", self.x` instead of `{self.x}` when resolve `x` as …
xizheyin 4ec9919
Add println! test for sugg-field-in-format-string-issue-141136
xizheyin 84f67a5
Downgrade the confident of suggestion `available field in format stri…
xizheyin 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
15 changes: 15 additions & 0 deletions
15
tests/ui/resolve/suggestions/sugg-field-in-format-string-issue-141136.rs
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,15 @@ | ||
struct Foo { | ||
x: i32 | ||
} | ||
|
||
impl Foo { | ||
fn foo(&self) { | ||
let _ = format!("{x}"); //~ ERROR cannot find value `x` in this scope [E0425] | ||
let _ = format!("{x }"); //~ ERROR cannot find value `x` in this scope [E0425] | ||
let _ = format!("{ x}"); //~ ERROR invalid format string: expected `}`, found `x` | ||
let _ = format!("{}", x); //~ ERROR cannot find value `x` in this scope [E0425] | ||
println!("{x}"); //~ ERROR cannot find value `x` in this scope [E0425] | ||
} | ||
} | ||
|
||
fn main(){} |
48 changes: 48 additions & 0 deletions
48
tests/ui/resolve/suggestions/sugg-field-in-format-string-issue-141136.stderr
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,48 @@ | ||
error: invalid format string: expected `}`, found `x` | ||
--> $DIR/sugg-field-in-format-string-issue-141136.rs:9:28 | ||
| | ||
LL | let _ = format!("{ x}"); | ||
| - ^ expected `}` in format string | ||
| | | ||
| because of this opening brace | ||
| | ||
= note: if you intended to print `{`, you can escape it using `{{` | ||
|
||
error[E0425]: cannot find value `x` in this scope | ||
--> $DIR/sugg-field-in-format-string-issue-141136.rs:7:27 | ||
| | ||
LL | let _ = format!("{x}"); | ||
| ^ | ||
| | ||
= help: you might have meant to use the available field in a format string: `"{}", self.x` | ||
|
||
error[E0425]: cannot find value `x` in this scope | ||
--> $DIR/sugg-field-in-format-string-issue-141136.rs:8:27 | ||
| | ||
LL | let _ = format!("{x }"); | ||
| ^^ | ||
| | ||
= help: you might have meant to use the available field in a format string: `"{}", self.x` | ||
|
||
error[E0425]: cannot find value `x` in this scope | ||
--> $DIR/sugg-field-in-format-string-issue-141136.rs:10:31 | ||
| | ||
LL | let _ = format!("{}", x); | ||
| ^ | ||
| | ||
help: you might have meant to use the available field | ||
| | ||
LL | let _ = format!("{}", self.x); | ||
| +++++ | ||
|
||
error[E0425]: cannot find value `x` in this scope | ||
--> $DIR/sugg-field-in-format-string-issue-141136.rs:11:20 | ||
| | ||
LL | println!("{x}"); | ||
| ^ | ||
| | ||
= help: you might have meant to use the available field in a format string: `"{}", self.x` | ||
|
||
error: aborting due to 5 previous errors | ||
|
||
For more information about this error, try `rustc --explain E0425`. |
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
Oops, something went wrong.
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.
What happens on
Does it essentially suggest
fn foo(&self) { _ = "{}", self.x }
(sic!)?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've opened issue #141350 to track this regression.
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 will give this message.
For further improvement, below two suggestions may be better?
The first suggestion is
and keep the origin suggestion
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, the message as emitted right now (on master) is not correct. It should indeed suggest
you might have meant to use the available field
as we do on beta/stable.