Jack Wrenn 3ce35a4ec5 Make Copy unsafe to implement for ADTs with unsafe fields ... As a rule, the application of `unsafe` to a declaration requires that use-sites of that declaration also require `unsafe`. For example, a field declared `unsafe` may only be read in the lexical context of an `unsafe` block. For nearly all safe traits, the safety obligations of fields are explicitly discharged when they are mentioned in method definitions. For example, idiomatically implementing `Clone` (a safe trait) for a type with unsafe fields will require `unsafe` to clone those fields. Prior to this commit, `Copy` violated this rule. The trait is marked safe, and although it has no explicit methods, its implementation permits reads of `Self`. This commit resolves this by making `Copy` conditionally safe to implement. It remains safe to implement for ADTs without unsafe fields, but unsafe to implement for ADTs with unsafe fields. Tracking: #132922		2024-12-07 20:50:00 +00:00
..
auxiliary
auto-traits.current.stderr
auto-traits.next.stderr
auto-traits.rs
copy-trait.rs
copy-trait.stderr
unsafe-fields-crate.rs
unsafe-fields-crate.stderr
unsafe-fields-parse.rs
unsafe-fields-parse.stderr
unsafe-fields.rs
unsafe-fields.stderr