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

RFC: Remove move/copy keywords in favor of type-based solution #3676

Closed
nikomatsakis opened this issue Oct 6, 2012 · 1 comment
Closed
Labels
A-typesystem Area: The type system

Comments

@nikomatsakis
Copy link
Contributor

As discussed here:

http://smallcultfollowing.com/babysteps/blog/2012/10/01/moves-based-on-type/

If we decide not to take this route, then I think there is a separate bug to rationalize our rules for when a value is moved and when it is not.

@catamorphism
Copy link
Contributor

This is implemented.

@catamorphism catamorphism reopened this Jan 3, 2013
@luqmana luqmana mentioned this issue Feb 15, 2013
bors added a commit that referenced this issue Feb 15, 2013
As per #4339/#3676 this pull removes all uses `move` and gets rid of parsing it in libsyntax.
So that's one more thing to cross off #4707
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-typesystem Area: The type system
Projects
None yet
Development

No branches or pull requests

2 participants