-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rustfmt.toml
proposal
#265
Conversation
We have not yet had any complaints about the default settings, is there a particular formatting gripe that motivated this? It will be a hard PR to take because it will cause conflicts across the board for all of us currently working in the repository. |
Totally fair. I should have explained this more but I more wanted to demonstrate what the In the meantime I will revert the changes to default settings. (Although personally I like the more condensed-code settings 😄 ) |
43597a5
to
1a20cf5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally in favor of explicit over implicit. We can change the defaults at a later time if we want. Can you also introduce this formatting requirement (along with the file itself) into https://github.com/FuelLabs/rfcs?
See: FuelLabs/rfcs#8 |
I agree that explicit is better than implicit, and we should start with the defaults for now for ease of adoption. If we have any gripes with the settings as they are, we can open subsequent bikeshedding issues for that. I just checked out this branch and verified that no diffs are generated by this toml, which is confirmed by the formatting check in actions. LGTM! |
I propose that we start using a
rustfmt.toml
file to illicit more regulated and more documented formatting requirements.See: https://rust-lang.github.io/rustfmt/?version=v1.4.36&search=