diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-01-19 08:15:05 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-01-19 08:15:05 +0100 |
| commit | 332f8f73ea581fd5cb2ee94c1b9ae31dd61d4d67 (patch) | |
| tree | 56a33d8bd48cb41e8ee6071ffa81c3b030da48ed /compiler/rustc_codegen_gcc | |
| parent | 987445cd42f1235c7599db9752f693459de31330 (diff) | |
| parent | aeeaed9ce137d489f7157202548d2ce3d65c60ae (diff) | |
| download | rust-332f8f73ea581fd5cb2ee94c1b9ae31dd61d4d67.tar.gz rust-332f8f73ea581fd5cb2ee94c1b9ae31dd61d4d67.zip | |
Rollup merge of #120107 - shepmaster:dead-code-repr-transparent, r=Nilstrieb
dead_code treats #[repr(transparent)] the same as #[repr(C)] In #92972 we enabled linting on unused fields in tuple structs. In #118297 that lint was enabled by default. That exposed issues like #119659, where the fields of a struct marked `#[repr(transparent)]` were reported by the `dead_code` lint. The language team [decided](https://github.com/rust-lang/rust/issues/119659#issuecomment-1885172045) that the lint should treat `repr(transparent)` the same as `#[repr(C)]`. Fixes #119659
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions