diff options
| author | bors <bors@rust-lang.org> | 2023-09-07 19:10:07 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-09-07 19:10:07 +0000 |
| commit | 1e746d7741d44551e9378daf13b8797322aa0b74 (patch) | |
| tree | 147bdfd98e0e16f4e0481ee570503a2e3261e63f /compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp | |
| parent | 70c7e4d21c7249af4222a10d09dc03286aa1e787 (diff) | |
| parent | 320bb8116f136f4748787cf92178da9e7e5b2d91 (diff) | |
| download | rust-1e746d7741d44551e9378daf13b8797322aa0b74.tar.gz rust-1e746d7741d44551e9378daf13b8797322aa0b74.zip | |
Auto merge of #115527 - oli-obk:drop_maybe_uninit_in_const, r=lcnr
Don't require `Drop` for `[PhantomData<T>; N]` where `N` and `T` are generic, if `T` requires `Drop` fixes https://github.com/rust-lang/rust/issues/115403 fixes https://github.com/rust-lang/rust/issues/115410 This was accidentally regressed in https://github.com/rust-lang/rust/pull/114134, because it was accidentally stabilized in #102204 (cc `@rust-lang/lang,` seems like an innocent stabilization, considering this PR is more of a bugfix than a feature). While we have a whole month to beta backport this change before the regression hits stable, I'd still prefer not to go through an FCP on this PR (which fixes a regression), if T-lang wants an FCP, I can can open an issue about the change itself.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions