News for hackers. Stuff that matters.
Re:The Serde Rust Framework by hawk_ on Friday October 15, 2021 @04:36AM (#28875645)
when Optional<u64> is used in rust what's the memory layout like? is the absence tracked using a pointer which is null or a bitvector of optional fields?
Re:The Serde Rust Framework by goldsteinq on Friday October 15, 2021 @04:49AM (#28875708)
Option<u64> would look like tagged union in memory, so one bit "tag", 8 bytes u64 and padding.

If type inside of Option<_> has invalid values (like references which can't be null) one of these would be used for None, so Option<&T> is the same size as &T.

Re:The Serde Rust Framework by ahahahahah on Friday October 15, 2021 @08:27PM (#28884591)
> If type inside of Option<_> has invalid values

Can it actually use any general invalid bit pattern? I expect that it only supports an optimization for values that cannot be zero (and then it uses zero to indicate None).

Re:The Serde Rust Framework by hawk_ on Friday October 15, 2021 @05:09AM (#28875794)
thanks and is the padding for aligned access (wasted space) or just full byte (poor performance on non x86/64 like architecture)? because that's the interesting part as to what's the tradeoff chosen and whether a dev can choose a different one. Any doc references are appreciated.
Re:The Serde Rust Framework by Nullabillity on Friday October 15, 2021 @07:46AM (#28876725)
They are padded for aligned access, so on amd64 Option<u64> will be 16 bytes.[0] However, the unused discriminant values are counted as niches for enums wrapping that, so Option<Option<u64>> is still 16 bytes (for example).

[0]: https://play.rust-lang.org/?version=stable&mode=debug&editio...