mirror of
https://github.com/rust-lang/rust.git
synced 2025-02-13 07:24:00 +00:00
![]() PhantomData: fix documentation wrt interaction with dropck As far as I could find out, the `PhantomData`-dropck interaction *only* affects code using `may_dangle`. The documentation in the standard library has not been updated for 8 years and thus stems from a time when Rust still used "parametric dropck", before [RFC 1238](https://rust-lang.github.io/rfcs/1238-nonparametric-dropck.html). Back then what the docs said was correct, but with `may_dangle` dropck it stopped being entirely accurate and these days, with NLL, it is actively misleading. Fixes https://github.com/rust-lang/rust/issues/102810 Fixes https://github.com/rust-lang/rust/issues/70841 Cc `@nikomatsakis` I hope what I am saying here is right.^^ |
||
---|---|---|
.. | ||
auxiliary | ||
drop_order.rs | ||
drop-foreign-fundamental.rs | ||
drop-foreign-fundamental.stderr | ||
drop-if-let-binding.rs | ||
drop-on-empty-block-exit.rs | ||
drop-on-ret.rs | ||
drop-struct-as-object.rs | ||
drop-trait-enum.rs | ||
drop-trait-generic.rs | ||
drop-trait.rs | ||
drop-uninhabited-enum.rs | ||
drop-with-type-ascription-1.rs | ||
drop-with-type-ascription-2.rs | ||
dropck_legal_cycles.rs | ||
dropck-eyepatch-extern-crate.rs | ||
dropck-eyepatch-manuallydrop.rs | ||
dropck-eyepatch-reorder.rs | ||
dropck-eyepatch.rs | ||
dynamic-drop-async.rs | ||
dynamic-drop.rs | ||
issue-979.rs | ||
issue-2734.rs | ||
issue-2735-2.rs | ||
issue-2735-3.rs | ||
issue-2735.rs | ||
issue-10028.rs | ||
issue-17718-const-destructors.rs | ||
issue-21486.rs | ||
issue-23338-ensure-param-drop-order.rs | ||
issue-30018-nopanic.rs | ||
issue-35546.rs | ||
issue-48962.rs | ||
issue-90752-raw-ptr-shenanigans.rs | ||
issue-90752.rs | ||
issue-100276.rs | ||
issue-103107.rs | ||
no-drop-flag-size.rs | ||
nondrop-cycle.rs | ||
repeat-drop-2.rs | ||
repeat-drop-2.stderr | ||
repeat-drop.rs | ||
terminate-in-initializer.rs | ||
use_inline_dtor.rs |