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.

Sign up for GitHub

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

Jump to bottom

remove the copy keyword, make Copy represent implicitly copyable types #5522

Closed
thestinger opened this issue Mar 24, 2013 · 2 comments
Closed

remove the copy keyword, make Copy represent implicitly copyable types #5522

thestinger opened this issue Mar 24, 2013 · 2 comments
Labels
A-frontend Area: Compiler frontend (errors, parsing and HIR)

Comments

@thestinger
Copy link
Contributor

I think this is the consensus after quite a few discussions about this. Clone will be the way to explicitly copy an ownership tree (stops at @ boundaries).

In the future, a DeepClone trait could be implemented to copy past @ boundaries, but it will have to handle cycles to work in the general case.
@thestinger thestinger mentioned this issue Mar 24, 2013
Closed
@graydon
Copy link
Contributor

graydon commented Jun 19, 2013

Still legit, properly classified, not yet done. 2013-06-19.

@thestinger
Copy link
Contributor Author

The copy keyword is now gone, and Copy has been removed. Adding a trait for implicitly copyable types can be a separate issue not tied to backwards compatibility.

oli-obk pushed a commit to oli-obk/rust that referenced this issue May 2, 2020
@bors
Auto merge of rust-lang#5522 - CrazyRoka:match_vec_item, r=phansch
d13ffbe 
New  lint `match_vec_item`

Added new lint to warn a match on index item which can panic. It's always better to use `get(..)` instead.
Closes rust-lang#5500
changelog: New lint `match_on_vec_items`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-frontend Area: Compiler frontend (errors, parsing and HIR)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@graydon @thestinger