[RFC] Split Copy
trait in two traits: Pod
and Copy
#23016
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DO NOT MERGE NEEDS AN APPROVED RFC.
Pod
trait is used to mark types that can be cloned by simply copying its bytes on the stack.Copy
trait is used to mark types that are implictly copyable.Pod
can only be derived by structs/enums whose fields are alsoPod
Copy
can only be derived by types that arePod
, i.e.trait Copy: Pod {}
#[derive(Copy)]
syntax extension now derives both thePod
andCopy
traits.#[derive(Pod)]
syntax extension have been added to derive thePod
traitCell<T>
'sT: Copy
bound has been relaxed toT: Pod
, this lets you use it with a wider variety of types like iterators, which are not implicitly copyable.[breaking-change]s
Copy
trait, you'll have to manually implementPod
as well:impl<T> Copy for MyType<T> {} + impl<T> Pod for MyType<T> {}
#![derive(Copy)]
expand into two items, it was necessary to change the unstable#[derive]
API. This will likely break third-party#[derive]
extensions.I plon to finish writing a proper RFC by tomorrow, but here's the current draft.RFC
cc @aturon @nikomatsakis @tbu-
cc #21846