Apologies if this had already been mentioned but I wonder if “colony” might fall foul of some inclusive naming guidelines:

 https://dc.eater.com/2020/6/16/21291725/dc-indie-restaurant-owners-washingtonpost-op-ed-landlords

It seems I’m not the only person to think so.

Jonathan

> On 10 Feb 2021, at 06:17, Ville Voutilainen via Lib-Ext <lib-ext_at_[hidden]> wrote:
>
> On Wed, 10 Feb 2021 at 04:17, Jeff Garland via SG14
> <sg14_at_[hidden]> wrote:
>>
>>
>>
>> On Feb 9, 2021, at 6:41 PM, Nevin Liber <nevin_at_[hidden]> wrote:
>>
>> 
>>> On Tue, Feb 9, 2021 at 7:11 PM Jeff Garland via SG14 <sg14_at_[hidden]> wrote:
>>>
>>> unordered_list
>>> unordered_block_list
>>> unordered_bucket_array_list
>>> unordered_sparse_list
>>> unordered_change_list
>>> unordered_sparse_collection
>>> sparse_agglomeration
>>> sparse_aggregate
>>> sparse_list
>>> sparse_block_list
>>> or
>>> bucket_list ;)
>>
>>
>> I'm not sure what you want us to do with an unordered set of names.
>>
>> You are the one championing changing the name to one of these. My advice is to pick the best name, and write up the justification for why it is better than colony and why it is better than all the other names in your set.
>>
>>
>> It’s brainstorming. If I had to pick one I’d say unordered_sparse_list.
>
> return -ENORATIONALE;
>
> I don't understand what the term sparse is supposed to tell me about a
> list. If a list isn't sparse, it's broken.
> Colony also doesn't behave like a list performance-wise, considering
> all of its operations, so I don't know
> why we'd suggest that it's a list.
> _______________________________________________
> Lib-Ext mailing list
> Lib-Ext_at_[hidden]
> Subscription: https://lists.isocpp.org/mailman/listinfo.cgi/lib-ext
> Link to this post: http://lists.isocpp.org/lib-ext/2021/02/17806.php