Open RalfJung opened 2 months ago
This is a case where the macro fails to parse, and I assume that since it's formatted on one line and the closure only contains a single item rustfmt really wants to update the closure to not use braces.
If you formatted the matches!
call by hand like this rustfmt should leave it alone:
impl<'tcx> LateLintPass<'tcx> for UnqualifiedLocalImports {
fn check_item(&mut self, cx: &LateContext<'tcx>, item: &'tcx hir::Item<'tcx>) {
let hir::ItemKind::Use(path, _kind) = item.kind else { return };
let is_local_import = |res: &Res| {
matches!(
res,
hir::def::Res::Def(def_kind, def_id)
if def_id.is_local() && !matches!(def_kind, DefKind::Macro(_))
)
};
}
}
I'll add that If https://github.com/rust-lang/rustfmt/pull/5554 lands that's the formatting that the input would produce.
Here's some example code:
It's not the best code, that line is too long. So let's format it. Now we have:
Now the line is even longer! It's way past the 100 character limit.
I guess rustfmt is reluctant to introduce linebreaks inside a macro, but then it should just avoid touching this code -- but instead it makes things worse by putting the entire closure on a single line.