-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Remove the fmt! syntax extension #9919
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
@@ -222,9 +222,6 @@ pub fn syntax_expander_table() -> SyntaxEnv { | |||
span: None, | |||
} as @SyntaxExpanderTTItemTrait, | |||
None))); | |||
syntax_expanders.insert(intern(&"oldfmt"), |
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.
Is it worth replacing this with a syntax extension that .span_err
s with something like fmt! has been replaced by
format!``? (i.e. keep the fmt!
macro around until at least post-0.9.)
Similar to the obsolete syntax stuff, and the removal of auto_encode
.
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.
Hm, I actually think so. I also wouldn't be opposed to a NOTE at the end of all the errors pointing at the documentation for format!
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.
Neither would I.
It lived a good life, but its time has come. The groundwork is set for the official transition after the next snapshot (removal of XXX2 macros)
Updated to print out that |
} | ||
|
||
cx.expr_block(cx.block(fmt_sp, stms, Some(buf()))) | ||
base::MRExpr(ecx.expr_uint(sp, 2)) |
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 think 3
would be better. :P
It lived a good life, but its time has come. The groundwork is set for the official transition after the next snapshot (removal of XXX2 macros)
Link to a list of configurable lints in documentation changelog: none
It lived a good life, but its time has come. The groundwork is set for the
official transition after the next snapshot (removal of XXX2 macros)