Repository navigation
Guard the rustfmt config that rustfmt reads, and default to field init shorthand - #8
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
cargo fastfmtnow puts itsdisable_all_formattingguard in therustfmt.tomlthat rustfmt reads for each package: the nearest one from the package directory up to the repository root. It creates a new file in the package directory only when there is none. Previously it created a guard-onlyrustfmt.tomlbeside every sub-package'sCargo.toml, even when the root guard already covered it, and those files hid root settings such asmax_width.fastfmt also runs rustfmt with
use_field_init_shorthand = true, which writesFoo { x: x }asFoo { x }. Likeuse_small_heuristics, it overrides the project'srustfmt.toml. Projects no longer need to set it themselves.See "Install and use" in the README.