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
RUST-993 Implement Clone for Collection<T> #454
Conversation
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.
LGTM! I took a look at the failures in the evergreen patch and they look to be known flaky tests.
Tagging in the other members of the team for review.
Once this PR is ready to merge, just hit the "Squash and Merge" button and make sure the commit title matches the PR title (i.e. includes ticket number and brief description). |
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.
LGTM!
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.
lgtm!
Because derive is too conservative, derive only implements Clone for Collection<T> if T is Clone. Collection<T> does not actually store any value of type T (so T does not need to be Clone).
Because derive is too conservative, derive only implements Clone for Collection<T> if T is Clone. Collection<T> does not actually store any value of type T (so T does not need to be Clone).
Because derive is too conservative, derive only implements Clone for Collection<T> if T is Clone. Collection<T> does not actually store any value of type T (so T does not need to be Clone).
Because
derive
is too conservative,derive
only implements Clone forCollection<T>
if T is Clone.Collection<T>
does not actually store any value of type T (so T does not need to be Clone).