-
Notifications
You must be signed in to change notification settings - Fork 963
Open
Labels
C-feature-requestCategory: a feature request (not decided/implemented)Category: a feature request (not decided/implemented)S-blockedStatus: blocked on rustc, an RFC, impl work, etc.; please also add a block reason labelStatus: blocked on rustc, an RFC, impl work, etc.; please also add a block reason label
Description
Given a snippet like this
unsafe fn foobar() {
core::arch::asm!("{}",
const X)
}I'd expect that to format to
unsafe fn foobar() {
core::arch::asm!("{}", const X)
}but instead nothing happens. Given that these operands are quite new, I suspect this is an oversight.
I'd happily look into fixing this, but I'm not 100% clear on whether the formatting behavior for existing code can be change? Though here I'd clearly consider it a bug.
Metadata
Metadata
Assignees
Labels
C-feature-requestCategory: a feature request (not decided/implemented)Category: a feature request (not decided/implemented)S-blockedStatus: blocked on rustc, an RFC, impl work, etc.; please also add a block reason labelStatus: blocked on rustc, an RFC, impl work, etc.; please also add a block reason label