mirror of
https://github.com/rust-lang/rust.git
synced 2025-04-30 20:17:50 +00:00
![]() Instead, we adopt the position that introducing an `unsafe` field itself carries a safety invariant: that if you assign an invariant to that field weaker than what the field's destructor requires, you must ensure that field is in a droppable state in your destructor. See: - https://github.com/rust-lang/rfcs/pull/3458#discussion_r1971676100 - https://rust-lang.zulipchat.com/#narrow/channel/213817-t-lang/topic/unsafe.20fields.20RFC/near/502113897 |
||
---|---|---|
.. | ||
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 |