-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Cleanup: Consistently use Param
instead of Arg
#62426
Comments
Can I work on this? |
Error: Only Rust team members can assign other users Please let |
@kper you can assign to yourself with |
@rustbot kper |
@kper it's already "assign"ed to you. |
I tried to begin with the renaming and I have been wondering how aggressive I should rename? It is kind of hard for me to see when I have real arguments or parameters. My first try (Commit 6c9051c as referenced above) led to extremely a lot of change. Can I have some feedback? In addition, I noticed that the issue has a "blocked" label. Should I therefore wait until #61856 is finished? |
I think that's a good idea.
This looks largely right, tho I didn't look at Please also avoid running |
#61856 has been merged |
@Centril can you look over my commit? :) |
@kper Can you file it as a PR? Easier to review that way. |
@Centril sure :) |
For example, ideally
fn visit_arg
would be namedfn visit_param
since this is about formal parameters (in function signatures and from the POV inside the function body) instead of actual arguments (the values you pass to functions).The type
Arg
should probably be namedParam
.(This is not an exhaustive list, there are other places "arg" is used not mentioned here that should probably use "param" instead)
cc @petrochenkov @c410-f3r
cc #61856
This issue has been assigned to @kper via this comment.
The text was updated successfully, but these errors were encountered: