forked from rust-lang/rust
-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Rollup merge of rust-lang#124692 - workingjubilee:document-no-double-pointer-coercion-happens, r=compiler-errors We do not coerce `&mut &mut T -> *mut mut T` Resolves rust-lang#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?
- Loading branch information
Showing
2 changed files
with
62 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
// Documents that Rust currently does not permit the coercion &mut &mut T -> *mut *mut T | ||
// Making this compile was a feature request in rust-lang/rust#34117 but this is currently | ||
// "working as intended". Allowing "deep pointer coercion" seems footgun-prone, and would | ||
// require proceeding carefully. | ||
use std::ops::{Deref, DerefMut}; | ||
|
||
struct Foo(i32); | ||
|
||
struct SmartPtr<T>(*mut T); | ||
|
||
impl<T> SmartPtr<T> { | ||
fn get_addr(&mut self) -> &mut *mut T { | ||
&mut self.0 | ||
} | ||
} | ||
|
||
impl<T> Deref for SmartPtr<T> { | ||
type Target = T; | ||
fn deref(&self) -> &T { | ||
unsafe { &*self.0 } | ||
} | ||
} | ||
impl<T> DerefMut for SmartPtr<T> { | ||
fn deref_mut(&mut self) -> &mut T { | ||
unsafe { &mut *self.0 } | ||
} | ||
} | ||
|
||
/// Puts a Foo into the pointer provided by the caller | ||
fn make_foo(_: *mut *mut Foo) { | ||
unimplemented!() | ||
} | ||
|
||
fn main() { | ||
let mut result: SmartPtr<Foo> = SmartPtr(std::ptr::null_mut()); | ||
make_foo(&mut &mut *result); //~ mismatched types | ||
//~^ expected `*mut *mut Foo`, found `&mut &mut Foo` | ||
make_foo(out(&mut result)); // works, but makes one wonder why above coercion cannot happen | ||
} | ||
|
||
fn out<T>(ptr: &mut SmartPtr<T>) -> &mut *mut T { | ||
ptr.get_addr() | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
error[E0308]: mismatched types | ||
--> $DIR/mut-mut-wont-coerce.rs:36:14 | ||
| | ||
LL | make_foo(&mut &mut *result); | ||
| -------- ^^^^^^^^^^^^^^^^^ expected `*mut *mut Foo`, found `&mut &mut Foo` | ||
| | | ||
| arguments to this function are incorrect | ||
| | ||
= note: expected raw pointer `*mut *mut Foo` | ||
found mutable reference `&mut &mut Foo` | ||
note: function defined here | ||
--> $DIR/mut-mut-wont-coerce.rs:30:4 | ||
| | ||
LL | fn make_foo(_: *mut *mut Foo) { | ||
| ^^^^^^^^ ---------------- | ||
|
||
error: aborting due to 1 previous error | ||
|
||
For more information about this error, try `rustc --explain E0308`. |