max_width is not stable/deterministic
Open
Nobody has claimed this yet.
C-bug
I-non-idempotency
P-low
SO-max_width
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 24
Description
If I have a repo that uses rustfmt defaults, (e.g. max_width=100), I can run
cargo fmt -- --config max_width=100
cargo fmt -- --config max_width=80
cargo fmt -- --config max_width=100
which will not restore the code to its original formatting but leave some modifications in place.
(for example seen on the cargo repo)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported sequence in a Rust repository such as cargo: run cargo fmt with max_width=100, then 80, then 100 again, and compare the result with the original formatting. Investigate why the final formatting is not restored; done means repeated configuration changes produce deterministic output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100