Closed
Description
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.
- Region -> Lifetime in general. While Region kinda makes more sense, we use Lifetime in the language
EarlyBoundRegion
->GenericLifetime
(to reflect what they are in the language)LateBoundRegion
->HigherRankedLifetime
(")*Folder
andfold_*
->*Replacer
andreplace_*
Substs
->GenericArgs
subst
->replace_generics
Mentors or Reviewers
Process
The main points of the Major Change Process are as follows:
- File an issue describing the proposal.
- A compiler team member or contributor who is knowledgeable in the area can second by writing
@rustbot second
.- Finding a "second" suffices for internal changes. If however, you are proposing a new public-facing feature, such as a
-C flag
, then full team check-off is required. - Compiler team members can initiate a check-off via
@rfcbot fcp merge
on either the MCP or the PR.
- Finding a "second" suffices for internal changes. If however, you are proposing a new public-facing feature, such as a
- Once an MCP is seconded, the Final Comment Period begins. If no objections are raised after 10 days, the MCP is considered approved.
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.