-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Remove internal uses of the NoCopy
marker
#19832
Conversation
I think that we currently have an |
NoCopy
markerNoCopy
marker
@alexcrichton To move forward, I changed the PR to just remove all the internal uses of |
marker: marker::NoCopy | ||
} | ||
#[allow(missing_copy_implementations)] | ||
pub struct OsRng; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This may actually want to keep one private field to ensure that it cannot be constructed outside of this module.
Awesome, thanks @japaric! Just one small nit and otherwise r=me |
@alexcrichton Added a dummy private field to |
Remove internal uses of the `NoCopy` marker Reviewed-by: alexcrichton
Using a type alias for iterator implementations is fragile since this exposes the implementation to users of the iterator, and any changes could break existing code. This commit changes the iterators of `VecMap` to use proper new types, rather than type aliases. However, since it is fair-game to treat a type-alias as the aliased type, this is a: [breaking-change].
Remove internal uses of the `NoCopy` marker Reviewed-by: alexcrichton
Remove internal uses of the `NoCopy` marker Reviewed-by: alexcrichton
r? @aturon / @alexcrichton