-
Notifications
You must be signed in to change notification settings - Fork 69
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
Rename various internal things #451
Comments
This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed. cc @rust-lang/compiler @rust-lang/compiler-contributors |
@rustbot second (specifically, I would prefer if moved past the confusing "folder" and "substs" terminology, feels like it's long overdue - the other changes seem like they don't have to be done at the same time) |
@rustbot label -final-comment-period +major-change-accepted |
Proposal
There are some things in rustc that are named historically or just really oddly. I would like to rename them to reflect what they are without having to understand Rust's history and/or programming language design/theory jargon.
EarlyBoundRegion
->GenericLifetime
(to reflect what they are in the language)LateBoundRegion
->HigherRankedLifetime
(")*Folder
andfold_*
->*Replacer
andreplace_*
Substs
->GenericArgs
subst
->replace_generics
Mentors or Reviewers
@oli-obk, @eddyb
Process
The main points of the Major Change Process are as follows:
@rustbot second
.-C flag
, then full team check-off is required.@rfcbot fcp merge
on either the MCP or the PR.You can read more about Major Change Proposals on forge.
Comments
This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.
The text was updated successfully, but these errors were encountered: