What is misleading about the title? A custom encoding scheme is exactly what it suggests. Maybe it has been edited since your comment was posted?

▲

gpm 2 hours ago | parent | next [-]

I'd actually point at the other half of the title than the existing comment when being pedantic "Replacing [...] with a 64-Bit Word" isn't quite right, it was replaced with a manually packed 64-Bit Word and the occasional heap allocation.

I'm not sure being this pedantic is particularly useful in titles though...

	▲	Dylan16807 2 hours ago \| parent [-]
		It's worth calling out either way. It's not just an encoding scheme, it's a reasonably significant change in architecture.

▲

dymk 4 hours ago | parent | prev [-]

It wasn’t replacing one rust enum, it was replacing what are effectively multiple enums

▲

dzaima 4 hours ago | parent [-]

How so? It's replacing multiple enum variants, but just one enum, "enum Value".

(also; if anything, the title is implying the exact opposite of "Rust compiler was able to optimize ...", "Replacing a Rust [...] with [...]" is clearly moving away from Rust-magic to something else)

▲

Brian_K_White 2 hours ago | parent [-]

Probably in the sense that you can remove the word rust and nothing changes. It's not about some failure of rust to be efficient at enums, but the title says it is.

	▲	win311fwg 2 hours ago \| parent [-]
		'Enum' is ill-defined so the addition of Rust is significant as it indicates what one can expect with how data is structured. There is nothing in that speaks to the Rust compiler or Rust being inefficient or anything of the sort. It remains unclear where this idea is coming from. There is nothing in title that would send you there. Unless, again, the title was edited at some point?