Skip to content
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

refactor to use param naming where appropriate #3803

Merged
merged 2 commits into from
Sep 24, 2019

Conversation

calebcartwright
Copy link
Member

Resolves #3801

@calebcartwright
Copy link
Member Author

calebcartwright commented Sep 22, 2019

As part of 2.x, we may also want to see whether we should augment/rename any config options, for example: should https://github.com/rust-lang/rustfmt/blob/master/Configurations.md#fn_args_layout probably be fn_params_layout? Or should there be one option for params in a function signature, and another for args on calls?

@topecongiro topecongiro merged commit 9c2b375 into rust-lang:master Sep 24, 2019
@topecongiro
Copy link
Contributor

As part of 2.x, we may also want to see whether we should augment/rename any config options, for example: should https://github.com/rust-lang/rustfmt/blob/master/Configurations.md#fn_args_layout probably be fn_params_layout? Or should there be one option for params in a function signature, and another for args on calls?

Yeah, I think renaming it on bumping to 2.0 sounds good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Refactor Param vs. Arg naming
2 participants