Description
Proposal
Our generators are more commonly known as coroutines, while generators are a simpler feature. With my rfc about adding generators (that produce Iterators) appearing to not have any major blockers, I would like to fix this naming issue now, before beginning an implementation of generators. Having two different things called "generators" would be immensely confusing to both rustc devs and users.
So, in short: I would like to replace the word "generator" (any capitalization) from rustc and libstd with "coroutine". This includes, but is not limited to,
- function names
- trait names
- data structures
- diagnostics
- symbol names
- lang item names
Mentors or Reviewers
This is just a rename, once seconded and landed, anyone can review this work.
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 mergeon 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.