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

Tracking issue for RFC 2133: compiler-generated Clone impls for Arrays and Tuples #44496

Closed
3 tasks done
aturon opened this issue Sep 11, 2017 · 3 comments
Closed
3 tasks done
Labels
B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-lang Relevant to the language team, which will review and decide on the PR/issue.

Comments

@aturon
Copy link
Member

aturon commented Sep 11, 2017

This is a tracking issue for the RFC "compiler-generated Clone impls for Arrays and Tuples " (rust-lang/rfcs#2133).

Steps:

@aturon aturon added B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. T-lang Relevant to the language team, which will review and decide on the PR/issue. labels Sep 11, 2017
@arielb1
Copy link
Contributor

arielb1 commented Sep 11, 2017

The RFC has already been implementd and stabilized.

@arielb1
Copy link
Contributor

arielb1 commented Sep 11, 2017

So we just need to add documentation. I suppose our documentation is just as good as that for the Copy Trait

@TimNN TimNN added the C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC label Sep 17, 2017
@Mark-Simulacrum
Copy link
Member

It seems that the reference documents this at least implicitly, stating that tuples and arrays of Clone/Copy types get impl's for Copy/Clone by the compiler. So I'm closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-lang Relevant to the language team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

4 participants