bvandeusenandClaude Opus 5 550a34d8e2 fmt: rustfmt budgets macro arguments at 60 chars, not the 100-char line ...

Both new assertions fit well inside the 100-column limit and both were still
rejected. The governing setting is `fn_call_width` (60), applied to a macro's
argument list: `survivor.id, older.id, "the older row is the one that
survives"` is 62 characters, so rustfmt breaks it and pairs the two values on
one line with the message beneath.

The neighbouring `assert_eq!(survivor.name, "Grocery", "spelled the way the
caller asked")` was accepted at 59 characters of arguments, which is the
same rule agreeing rather than a different one.

rustfmt's own output, pasted back. Second time this lane has caught the same
class of thing in one session — the other was a method chain, budgeted at 60
by `chain_width`. Recorded so the next person reaches for the 60, not the 100.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01K3MMqUtzX1TJgA1oypvm1c

2026-08-31 16:52:00 -04:00

..

src

fmt: rustfmt budgets macro arguments at 60 chars, not the 100-char line

2026-08-31 16:52:00 -04:00

Cargo.toml

android: the binding generator gets its own crate, free of the app's deps

2026-08-18 15:54:10 -04:00

uniffi.toml

android: bind the core to Kotlin through uniffi (M12 step 4)

2026-08-18 11:09:52 -04:00