Skip to content

Conversation

alexcrichton
Copy link
Member

This also prevents future fmt! usage from leaking into the compiler, but it's still turned on by default for everyone else.

Copy link
Contributor

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?

@huonw
Copy link
Contributor

huonw commented Sep 29, 2013

Needs a rebase (surprise surprise!), and I think it may be worth making fmt! print a warning on use (or even just .span_note) to make the transition slightly easier for users.

@alexcrichton
Copy link
Member Author

Aha, now make check passes!

@huonw
Copy link
Contributor

huonw commented Sep 30, 2013

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).
bors added a commit that referenced this pull request Oct 1, 2013
This also prevents future fmt! usage from leaking into the compiler, but it's still turned on by default for everyone else.
@bors bors closed this Oct 1, 2013
@bors bors merged commit dec3705 into rust-lang:master Oct 1, 2013
flip1995 pushed a commit to flip1995/rust that referenced this pull request Oct 6, 2022
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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants