3 ms·
One consequence is that you end with cute names instead of clear names. Cherry picking from the top 30 or so crates: - parking_lot - hashbrown - ryu - heck
by sa46 4y ago
One consequence is that you end with cute names instead of clear names. Cherry picking from the top 30 or so crates:
- parking_lot
- hashbrown
- ryu
- heck
The longer there's a shared namespace, the stranger the names get as the "good" names are already in use.
- tialaramex 4y agoFor implementations of a known idea, I would rather have a fun codename than see the word for the idea used to also name the implementation. The contrary case gets confusing fast. "Oh Known Algorithm doesn't work" "Huh, I read a paper which proved it works" "No, I mean, Known Algorithm, not known algorithm". "What?" "The implementation by Popular Author. It's broken for the case we care about". "Can't they fix it?" "They say that although their implementation is called Known Algorithm it's just better that it not fix this because now Known Algorithm is different from the known algorithm". What? Knowing there's a problem, or a different performance trade off, or a lack of maintenance for Haphazard (Jon Gjengset's Hazard Pointers implementation) is very different from having a problem with Hazard Pointers the idea.