-
Notifications
You must be signed in to change notification settings - Fork 1.7k
uninlined-format-args suggests broken code for assert! macros in 2018 edition #10234
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
Comments
This was fixed in rust-lang/rust@e5010c9 (#10055), but that patch is only included in 1.68 and later, not 1.67. |
In https://github.com/tokio-rs/tls/actions/runs/4021612870/jobs/6910637824 I noticed this for a plain |
@djc I don't think it's a false positive. format_args_capture for |
That's fair, thanks! |
One error had to be ignored for now due to the false positive in rust-lang/rust-clippy#10234, which is fixed in 1.68.
One error had to be ignored for now due to the false positive in rust-lang/rust-clippy#10234, which is fixed in 1.68.
Should this be closed? |
Summary
uninlined-format-args
, which is now enforced by default, complains about format literals passed to theassert!
macros, but inlined format args don't work with them in 2018 edition.Reproducer
I tried this code:
I expected to see this happen: this to work as suggested by clippy
Instead, this happened: compilation warning +
foo is {hey}
being a panic message instead offoo is 42
Version
Additional Labels
No response
The text was updated successfully, but these errors were encountered: