Yacin Tmimi

There's some type of `Shape` issue here. If you add one more character to the function name or to the return type, then it wraps: ```rust mod tests { //...

rustfmt has never had dedicated support for the `asm!` macro. I put something together a while ago (https://github.com/rust-lang/rustfmt/pull/5191), but that open PR is fairly out of date and I'm sure...

> Also, while maybe it's not been decided exactly what the formatting should look like, it is more functional for certain syntax components that are older, e.g. this > >...

Marking this as blocked on https://github.com/rust-lang/style-team/issues/152

What version of rustfmt are you using? When I build and run rustfmt from source (version: rustfmt 1.8.0-nightly (5619b64461 2025-02-12)), I get the same output for all edition values. So...

I realize now that setting `--edition` was a false negative. I should have been setting `--style-edition`. With that config I was able to reproduce the issue. I believe the PR...

Based on the [Style Guild section for function definitions](https://doc.rust-lang.org/nightly/style-guide/items.html#function-definitions) this formatting doesn't seem correct to me. I'd expect something like this: ```rust trait Foo { fn fooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo( _: () )...

@fmease looks like we're not handling the `AssocItemKind::Delegation` and `AssocItemKind::DelegationMac` variants here: https://github.com/rust-lang/rustfmt/blob/ee329d33c896da13ae5b08fe6d31724108cbdfcb/src/visitor.rs#L668

Please provide a code snippet that can be used to reproduce this error.

It would be very helpful if you could extract a minimal reproducible example that someone can use to run rustfmt against.