237

Oh yea, that's the good stuff huffs glue (programming.dev)

submitted 11 months ago by tatterdemalion@programming.dev to c/programmer_humor@programming.dev

22 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] GissaMittJobb@lemmy.ml 12 points 11 months ago

Since all of the expressions just wrap a None, I wouldn't be surprised if the transmutes basically get compiled to 0, making the assertion at the end assert_eq!(0 * 0, 0).

[-] tatterdemalion@programming.dev 9 points 11 months ago* (last edited 11 months ago)

Nah these are the actual integer representations. Otherwise you would have Some(None) == Some(Some(None)) which is way too Javascripty for Rust folks.

[-] GissaMittJobb@lemmy.ml 3 points 11 months ago

That's kind of wild, I double-checked and it's true.

Although I disagree with the second part, the Rust folks wouldn't care about the in-memory representation as long as the compilation is on point.

Looking closer at the final enum, I guess it's because there are nine possible cases for it, making the compiler pack it into 4 bits, with one number representing each? I checked and None is represented as 8, while 7 Somes containing a None is 0 and the full 8 Somes is represented by 1.