diff options
| author | bors <bors@rust-lang.org> | 2023-05-13 00:23:51 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-05-13 00:23:51 +0000 |
| commit | 9850584a4e5e4b7e5cebd9d90c27d8b88591f264 (patch) | |
| tree | 2f1d08489c9e1743b075f64744ede1c83fd1cec2 /tests/rustdoc-ui/coverage/allow_missing_docs.rs | |
| parent | 7d59fa3d23f021a18289416caf79fdf050bbc3b0 (diff) | |
| parent | b93fd8355acbe8a4ffd53ad32c3d7f4798c15b98 (diff) | |
| download | rust-9850584a4e5e4b7e5cebd9d90c27d8b88591f264.tar.gz rust-9850584a4e5e4b7e5cebd9d90c27d8b88591f264.zip | |
Auto merge of #103413 - RalfJung:phantom-dropck, r=lcnr
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.^^
Diffstat (limited to 'tests/rustdoc-ui/coverage/allow_missing_docs.rs')
0 files changed, 0 insertions, 0 deletions