-
Couldn't load subscription status.
- Fork 13.9k
Document why not use concat! in dbg! macro #81233
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
|
r? @m-ou-se (rust-highfive has picked a reviewer for you, use r? to override) |
|
Thanks! @bors r+ rollup |
|
📌 Commit 6f22803e052bfdcb0a4879940b5a3509ac890340 has been approved by |
|
🌲 The tree is currently closed for pull requests below priority 1000. This pull request will be tested once the tree is reopened. |
Co-authored-by: Miguel Ojeda <ojeda@users.noreply.github.com>
|
@bors r+ rollup |
|
📌 Commit d0c1405 has been approved by |
Rollup of 10 pull requests Successful merges: - rust-lang#80573 (Deny rustc::internal lints for rustdoc and clippy) - rust-lang#81173 (Expand docs on Iterator::intersperse) - rust-lang#81194 (Stabilize std::panic::panic_any.) - rust-lang#81202 (Don't prefix 0x for each segments in `dbg!(Ipv6)`) - rust-lang#81225 (Make 'docs' nullable in rustdoc-json output) - rust-lang#81227 (Remove doctree::StructType) - rust-lang#81233 (Document why not use concat! in dbg! macro) - rust-lang#81236 (Gracefully handle loop labels missing leading `'` in different positions) - rust-lang#81241 (Turn alloc's force_expr macro into a regular macro_rules.) - rust-lang#81242 (Enforce statically that `MIN_NON_ZERO_CAP` is calculated at compile time) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Original title: Reduce code generated by
dbg!macroThe expanded code before/after: https://rust.godbolt.org/z/hE3j95.
We cannot use
concat!sincefile!could contains{or the expression is a block ({ .. }).Using it will generated malformed format strings.
So let's document this reason why we don't use
concat!macro at all.