I'm using the feature "Newtype" to follow the orphan rules, but I wondered if I can make my new type totally the same as the old one, for example: struct Foo; #[derive(Deref)] struct Bar(Foo); fn foos(foos: &[Foo]) { } fn main() { let bars = vec!{Bar{0: Foo{}}, Bar{0: Foo{}}, Bar{0: Foo{}}}…

[image] psionic12: Is the memory layout of Bar and Foo are the same? (in the real code, I even add Repr(C) to try to make the memory layout the same, but I'm not sure if it is useful). If it's not, how do I make them the same layout? It is not guaranteed if the struct is repr(Rust) (this is t…

Newtype problem: reinterpret_cast a &[Bar] to &[Foo]

help

jbe April 14, 2022, 1:19pm 13

I started a new thread where I'm asking about how wide-pointer casts are defined.

Topic		Replies	Views
Casting wide-pointers	18	3096	July 14, 2022
Have there been any proposals for improved ergnomics with #[repr(transparent)] newtypes help	6	599	September 19, 2020
Convert Arc<Foo> to Arc<Bar> if Bar is a newtype wrapper of Foo	2	137	July 1, 2024
Transmute() with container types help	14	662	July 13, 2022
Vec layout / transmute help	5	730	June 15, 2022

Newtype problem: reinterpret_cast a &[Bar] to &[Foo]

Related topics