-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Remove fmt! usage from the compiler #9599
Conversation
@@ -1357,7 +1357,7 @@ mod tests { | |||
let mut b = Bitv::new(14, true); | |||
b.clear(); | |||
do b.ones |i| { | |||
fail!("found 1 at %?", i) | |||
fail2!("found 1 at %?", i) |
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.
this one and the next is still using %?
, is that correct?
Needs a rebase (surprise surprise!), and I think it may be worth making |
Aha, now |
It doesn't pass github's automatic-merge-detector though. |
We're not outright removing fmt! just yet, but this prevents it from leaking into the compiler further (it's still turned on by default for all other code).
This also prevents future fmt! usage from leaking into the compiler, but it's still turned on by default for everyone else.
Add a temporary workaround for multiline formart arg inlining per suggestion in rust-lang#102729 (comment) workaround for an internal crash when handling multi-line format argument inlining. changelog: none (no point for changelog because it is still a new lint being introduced)
This also prevents future fmt! usage from leaking into the compiler, but it's still turned on by default for everyone else.