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

Implement Clone for generators #494

Closed
1 of 3 tasks
canndrew opened this issue Mar 6, 2022 · 7 comments
Closed
1 of 3 tasks

Implement Clone for generators #494

canndrew opened this issue Mar 6, 2022 · 7 comments
Labels
I-lang-nominated major-change A proposal to make a major change to rustc major-change-accepted A major change proposal that was accepted T-compiler Add this label so rfcbot knows to poll the compiler team

Comments

@canndrew
Copy link

canndrew commented Mar 6, 2022

Proposal

It would be nice if generators, like closures, could automatically implement Clone and Copy where possible. Is this something that the lang team would consider desirable? (It would certainly be useful to me).

There is some prior discussion of this on zulip here: https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/.60Clone.60.20for.20generators

Mentors or Reviewers

@tmandry? @estebank?

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.
  • 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.

@canndrew canndrew added major-change A proposal to make a major change to rustc T-compiler Add this label so rfcbot knows to poll the compiler team labels Mar 6, 2022
@rustbot
Copy link
Collaborator

rustbot commented Mar 6, 2022

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 rustbot added the to-announce Announce this issue on triage meeting label Mar 6, 2022
@canndrew
Copy link
Author

I have implemented this here: https://github.com/canndrew/rust/tree/clone-generators

Would someone be willing to review it?

@apiraino apiraino removed the to-announce Announce this issue on triage meeting label Mar 17, 2022
@oli-obk
Copy link
Contributor

oli-obk commented Mar 20, 2022

@rustbot second

@rustbot rustbot added the final-comment-period The FCP has started, most (if not all) team members are in agreement label Mar 20, 2022
@nikomatsakis
Copy link
Contributor

@rustbot label +I-lang-nominated

Let's discuss this briefly in the lang meeting, but it seems good to me. The idea is to make generators implement Clone/Copy if they can, just as closures do now.

@nikomatsakis
Copy link
Contributor

We discussed this in today's @rust-lang/lang meeting and the general consensus was that we were in favor of this change and that no RFC was required (this can be considered a logical extension of rust-lang/rfcs#2132. It would still require a tracking issue and an FCP on the PR that implements it -- it would also be good, @canndrew, to do a write-up of the proposed design for that issue (presumably a small one) to help guide the stabilization report.

@canndrew
Copy link
Author

Sorry for the delayed response. I've been busy with work/life.

I've updated the PR to pass the CI checks and I've opened a tracking issue which includes a short write-up of the feature. Is this write-up the sort of thing you had in mind?

@apiraino
Copy link
Contributor

@rustbot label -final-comment-period +major-change-accepted

@rustbot rustbot added major-change-accepted A major change proposal that was accepted to-announce Announce this issue on triage meeting and removed final-comment-period The FCP has started, most (if not all) team members are in agreement labels Mar 30, 2022
@apiraino apiraino removed the to-announce Announce this issue on triage meeting label Mar 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I-lang-nominated major-change A proposal to make a major change to rustc major-change-accepted A major change proposal that was accepted T-compiler Add this label so rfcbot knows to poll the compiler team
Projects
None yet
Development

No branches or pull requests

5 participants