diff options
| author | Alejandra González <blyxyas@gmail.com> | 2025-02-11 16:32:35 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-02-11 16:32:35 +0000 |
| commit | c40898e1868155a40a279610072d8010fefc1ca1 (patch) | |
| tree | 5bb40623a5ae8c3d05024f53c4671b8fd1f208cb /compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp | |
| parent | ff87bead4f4931de38194809b5c9a420cce732e6 (diff) | |
| parent | 58d483409705aa4063eec5edbe6bb020adcacb59 (diff) | |
| download | rust-c40898e1868155a40a279610072d8010fefc1ca1.tar.gz rust-c40898e1868155a40a279610072d8010fefc1ca1.zip | |
`declare_interior_mutable_const`, `borrow_interior_mutable_const`: resolve `<T as Trait>::AssocT` projections (#14125)
changelog: [`declare_interior_mutable_const`, `borrow_interior_mutable_const`]: resolve `<T as Trait>::AssocT` projections --- This came up during https://github.com/rust-lang/rust/pull/130543 where we have `<T as AtomicPrimitive>::Assoc = AtomicT` instead of just `AtomicT` and clippy failed to resolve that properly. This really needs a review, because - I don't know if `try_normalize_erasing_regions` is the right thing to call here. - I'm not sure if I peel off the correct amount of `ValTree::Branch` layers (I think I do). Also, shouldn't this lint's infrastructure rely on `Freeze` trait (https://github.com/rust-lang/rust/issues/121675) instead of hardcoding a list of known-to-be-interior-mutable types? --- Previously filed this in the main rust repo (https://github.com/rust-lang/rust/pull/136369), was asked to do it here instead (https://github.com/rust-lang/rust/pull/136369#issuecomment-2628527774).
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions