Alan-Chen99

Nice! the transmute I gave above does the same thing, but you can also make them work with, say, vectors. > So is this similar to [cell-gc](https://github.com/jorendorff/cell-gc#understanding-heaps) or [gc-arena](https://github.com/kyren/gc-arena/blob/master/src/gc-arena/tests/tests.rs#L48-L56) where...

> Can you make https://github.com/CeleritasCelery/rune/issues/26#issuecomment-1529038816 sample code compile using transmutes? This will work with the raw conversion method. But I couldn't make it work with transmute. This isn't supposed to...

UnsafeCell and &mut should make a difference in theory. In practice it doesn't (for now), due to things like https://github.com/rust-lang/rust/issues/71354. It will probably make a difference in future versions of...

> Seems like the tradeoff is increased verbosity though Yea, the verbosity is no good. If we do adopt this we need a good abstraction over this using macros. I...

What if we keep two formats of string: 1) rust strings 2) vector of chars some operations will demand 1) (inserts) and some 2) (regex). we covert to whatever we...

By vector of chars I mean you make a vec for a struct char that can be any char. Aliasing just means that we need to "box" the string and...

What if we keep two formats of string: 1) rust strings 2) vector of chars some operations will demand 1) (inserts) and some 2) (regex). we covert to whatever we...

What if for non-simple types, we store a raw pointer to ObjectHeader (heap) which we should be able to get an offset (at compile time)

I would think that you do all the conversion as raw pointers. This shouldn't violate provenance since the province you originally got the object is the whole object (and miri...

Also, currently cons are 24 bytes. Would we benefit from shrinking to 16?