Strange code generated in enum_map_derive? about enum-map HOT 2 CLOSED

Thanks for quick reaction!

w.r.t. why it was this way: I'm looking at handle_named_variant and that looks very similar except in that case we have fields which means < comparison catches it: perhaps unit was modeled on it and never adapted to do something more efficient. Maybe a range match is better there or something but that's for another day – unit variant is what I care about in this ticket.

from enum-map.

handle_named_variant uses < because it needs to (the number of variants is variable for named variants), and I assume handle_unit_variant got < from it.

As for why if is used rather than match, this is because match arms don't accept const expressions (inline-const is currently nightly only - rust-lang/rust#76001). At some point I think I would like to implement a special case for enums that only have unit variants that uses match for those (to shorten compilation times when having a lot of enums), but I didn't do that yet

from enum-map.