Erasures use unspecified techniques of constant time complexity
to identify the memory locations of erased elements,
which are subsequently skipped during iteration,
as opposed to relocating subsequent elements during erasure.
Active block capacities have
an implementation-defined growth factor
(which need not be integral),
for example a new active block's capacity could be equal to
the summed capacities of the pre-existing active blocks.
The default limits of an implementation are not guaranteed to be the same as
the minimum and maximum possible capacities
for an implementation's element blocks.
If user-specified limits passed to
a hive constructor or reshape
are not within hard limits, or
if the specified minimum limit is greater than the specified maximum limit,
the behavior is erroneous and the effects are
implementation-defined.
An element block is said to be within the bounds
of a pair of minimum/maximum limits
when its capacity is greater-or-equal-to the minimum limit and
less-than-or-equal-to the maximum limit.
Descriptions are provided here only for operations on hive
that are not described in that table or for operations
where there is additional semantic information.