-
-
Notifications
You must be signed in to change notification settings - Fork 14.5k
rustc_parse_format: improve diagnostics for unsupported debug = syntax #150897
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
Conversation
|
rustbot has assigned @JonathanBrouwer. Use |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
140bb59 to
b56dc0f
Compare
This comment has been minimized.
This comment has been minimized.
|
☔ The latest upstream changes (presumably #151003) made this pull request unmergeable. Please resolve the merge conflicts. |
b56dc0f to
1c6894f
Compare
|
Some changes occurred in src/tools/cargo cc @ehuss |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
1c6894f to
3db61bc
Compare
|
r? @estebank |
This comment has been minimized.
This comment has been minimized.
3db61bc to
f92a01c
Compare
This comment has been minimized.
This comment has been minimized.
f92a01c to
5e2726f
Compare
This comment has been minimized.
This comment has been minimized.
5e2726f to
667538e
Compare
|
@estebank thanks for the review. I made the necessary changes. |
667538e to
9817ec2
Compare
This comment has been minimized.
This comment has been minimized.
Detect Python-style f-string debug syntax in format strings and emit a
clear diagnostic explaining that it is not supported in Rust. When the
intended operation can be inferred, suggest the corresponding Rust
alternative e.g from `println!("{=}", x)` to `dbg!({x})`.
Signed-off-by: Usman Akinyemi <usmanakinyemi202@gmail.com>
9817ec2 to
0061a22
Compare
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
|
@bors r+ rollup |
|
❌ Encountered an error while executing command |
rustc_parse_format: improve diagnostics for unsupported debug = syntax
Detect Python-style f-string debug syntax in format strings and emit a
clear diagnostic explaining that it is not supported in Rust. When the
intended operation can be inferred, suggest the corresponding Rust
alternative (e.g. `dbg!` for `{x=}`).
…uwer Rollup of 7 pull requests Successful merges: - #151960 (rustc_parse: improve the error diagnostic for "missing let") - #152157 (Fix error spans for `asm!()` args that are macros) - #152317 (fix: sup_trace to sub_trace) - #150897 (rustc_parse_format: improve diagnostics for unsupported debug = syntax) - #151154 (Add `s390x-unknown-none-softfloat` with `RustcAbi::Softfloat`) - #152013 (Update to Xcode 26.2) - #152326 (Remove the compiler adhoc group)
Rollup merge of #150897 - Unique-Usman:ua/debug, r=estebank rustc_parse_format: improve diagnostics for unsupported debug = syntax Detect Python-style f-string debug syntax in format strings and emit a clear diagnostic explaining that it is not supported in Rust. When the intended operation can be inferred, suggest the corresponding Rust alternative (e.g. `dbg!` for `{x=}`).
Detect Python-style f-string debug syntax in format strings and emit a
clear diagnostic explaining that it is not supported in Rust. When the
intended operation can be inferred, suggest the corresponding Rust
alternative (e.g.
dbg!for{x=}).