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

Document that T: Copy + Clone should have "obvious" Clone impl #33416

Closed
alexcrichton opened this issue May 4, 2016 · 0 comments
Closed

Document that T: Copy + Clone should have "obvious" Clone impl #33416

alexcrichton opened this issue May 4, 2016 · 0 comments
Labels
B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Comments

@alexcrichton
Copy link
Member

Tracking issue for rust-lang/rfcs#1521

@alexcrichton alexcrichton added B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. labels May 4, 2016
durka added a commit to durka/rust that referenced this issue May 5, 2016
Adds documentation to Clone, specifying that Copy types should have a trivial Clone impl.

Fixes rust-lang#33416.
Manishearth added a commit to Manishearth/rust that referenced this issue May 8, 2016
implement RFC 1521

Adds documentation to Clone, specifying that Copy types should have a trivial Clone impl.

Fixes rust-lang#33416.

I tried to use "should" and "must" as defined [here](https://tools.ietf.org/html/rfc2119).

cc @ubsan
Manishearth added a commit to Manishearth/rust that referenced this issue May 8, 2016
implement RFC 1521

Adds documentation to Clone, specifying that Copy types should have a trivial Clone impl.

Fixes rust-lang#33416.

I tried to use "should" and "must" as defined [here](https://tools.ietf.org/html/rfc2119).

cc @ubsan
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. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

2 participants