Subject: Re: [isocpp-lib-ext] std::colony name brainstorming
From: Ville Voutilainen (ville.voutilainen_at_[hidden])
Date: 2021-02-10 09:32:40
On Wed, 10 Feb 2021 at 16:45, Jeff Garland
> > Right. But sparse vs. dense matrices are what I think about when I see
> > a suggestion for a sparse list,
> > and I don't see how this std::hive (yay, surreptitious sleight-of-hand
> > in play, caveat emptor :P) is more
> > sparse than a linked list, it seems *less* sparse because there are
> > allocated-but-skipped slots in it.
> Ok â if I follow youâre saying a âsparse matrixâ representation would have less storage per unit size than a âdense matrixâ. Interesting.
What do you mean "by unit size"? But, well, what I mean is below..
> > I would certainly imagine that a sparse array would try to optimize
> > storage for particular values in it, and I don't
> > think std::hive does that.
> Yes, I see.
> >> Letâs take a look at some of the other âanalogy namesâ that have been suggested. I see âhotelâ, âparking lotâ, and âhiveâ. I like âhiveâ very much. Unfortunately, a hive is random access.
> > If you crack it open. The ones designed to be opened without cracking
> > are nests, not hives. :P
> > (Or so I read from the internets, hives are natural, nests are
> > artificial. Go figure, I don't know whether
> > that difference is correct.). The normal access to either isn't
> > random, though; bees don't just go directly
> > anywhere in the hive or nest, there are some pathways they need to follow.
> Unfortunately the hexagonal slot pattern is burned into the image of a âhiveâ â very ordered cells.
That doesn't make it random-access from the point of view of how bees
go from outside to cell $foo,
or how they go from cell $foo to outside. There's tunnels and layers
and storage structures, and no
random access because, well, if a bee is looking for a cell that has
$bar amount of honey in it,
there's an access that needs to look at more cells than just going
straight to the right one. Some of
those cells are in a skip list. :P
> Thatâs fair. The thing is that the âfleeting natureâ of elements in a colony is much more like the âmoving trafficâ that comes and goes than the buildings. Although, to be fair, the use case involves both kinds of elements â some mostly static and some that come and go quickly.
> Iâm not strongly against âhiveâ at this point, itâs better than âcolonyâ in my opinion. Just not sure itâs better than block_list or some other function describing variant.
That does seem like an alternative that describes the structure more
than it does describe the purpose. But, then again,
that's somewhat consistent with what we've had before. But also
somewhat inconsistent, an unordered_map is not
SG14 list run by email@example.com
Older Archives on Google Groups