Subject: std::colony name brainstorming
From: Ben Craig (ben.craig_at_[hidden])
Date: 2021-02-08 11:43:08
The paper talks a lot about the name colony, and that the name âbagâ isnât a good fit. I want to see if we can have other good names (or name pieces) get discussed on the mailing list.
For picking names, I like using a name as a way to compare and contrast against similar choices. Ideally, the name should indicate why you would use one facility over another.
The big reasons I see to prefer colony over another container:
* Pointer and iterator stability
* Contiguous block storage for faster iteration (i.e. not a node based container)
* O(1) inserts and deletes
* Re-orderable / sortable
Reasons to use other containers:
* Contiguous elements
* Sub-linear lookup
* Sorted by default
* User control over insert location
I donât see a good way to tease out the subtle contiguity differences in a short name. The stability aspect isnât too hard thoughâ¦ âstable_<foo>â can communicate thatâ¦ assuming we can find a suitable <foo>. The main downside to âstable_â is all the node based containers are already stable, but donât have the prefix.
Iâm leaning towards âstable_bundleâ. âbundleâ communicates a bit of disorganization. It still sounds like a container (âa bundle of intsâ). I donât think it has strong precedence in CS unlike so many other names. âbundleâ as the root is still rather arbitrary though. Neither part of the name communicates that fast iteration is a key aspect of the container.
We could attempt to fill <foo> with something that indicates the expected implementation strategy. Iâm less fond of that approach, but it can help communicate the design of the container. I can suggest âstable_skip_arrayâ and âstable_skip_listâ. Iâm not overly fond of âarrayâ or âlistâ in the names though, as they suggest layouts that arenât entirely accurate (single large allocation and individual element allocation respectively). Iâm not fond of âbucketâ since that has precedence in our hash map apis, though I could live with âstable_bucketâ.
A thesaurus item to start from: https://www.thesaurus.com/browse/array?s=t. Iâve browsed over list, container, and aggregate for other ideas.
Are there other aspects of the container we should look at for naming? Any suggestions for affixes or roots for a multi-part name?
SG14 list run by email@example.com
Older Archives on Google Groups