Raw pointers can be fat
Can someone explain to me how `Box::from_raw` and `Box::into_raw` are able to work with unsized types? Aren't we 100% for sure loosing the size/vtable? /cc @Gankro
-
-
-
So you're saying `mem::size_of::<*const [u8]>` is double width, right? Shouldn't the compiler be disallowing a cast from a fat raw pointer to a thin raw pointer? If `Box::<[u8]>::into_raw` goes through C, that will cause big problems right?
- 6 more replies
New conversation -
-
-
This Tweet is unavailable.
-
That doesn't apply to vtables, and we aren't necessarily using malloc
End of conversation
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.