diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-05-04 12:37:23 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-05-04 12:37:23 +0200 |
| commit | b0715b4e572d08e1d07963e6913d15a73b046c29 (patch) | |
| tree | e0289e6b01c3c886aecf3a14ba2b0f4f64de6205 /compiler/rustc_interface/src | |
| parent | 81b43b759cd7089479aff743993d058e0f381149 (diff) | |
| parent | e404e7a8bdca1d517ffa1c5b56ad2513413db9c3 (diff) | |
| download | rust-b0715b4e572d08e1d07963e6913d15a73b046c29.tar.gz rust-b0715b4e572d08e1d07963e6913d15a73b046c29.zip | |
Rollup merge of #124692 - workingjubilee:document-no-double-pointer-coercion-happens, r=compiler-errors
We do not coerce `&mut &mut T -> *mut mut T` Resolves #34117 by declaring it to be "working as intended" until someone RFCs it or whatever other lang proposal would be required. It seems a bit of a footgun, but perhaps there are strong reasons to allow it anyways. Seeing as how I often have to be mindful to not allow a pointer to coerce the wrong way in my FFI work, I am inclined to think not, but perhaps it's fine in some use-case and that's actually more common?
Diffstat (limited to 'compiler/rustc_interface/src')
0 files changed, 0 insertions, 0 deletions