Inherit/Insert Summary | |
| |
No developed. | |
No developed. |
Constructor Summary | |
capacity of the set is
initialized using the Default_size value. Then, tuning of needed
storage size is done automatically according to usage. If you
are really sure that your set is always really bigger than
Default_size, you may use with_capacity to save some execution time.
| |
capacity . Thus, this feature may be used
in place of make to save some execution time if one is sure that
storage size will rapidly become really bigger than Default_size (if
not sure, simply use make ). Anyway, the initial medium_size value
is just an indication and never a limit for the possible
capacity . Keep in mind that the capacity tuning is done
automatically according to usage.
|
Slot Summary | |
| |
buckets storage area is the primary hash table of capacity
elements. To search some element, the first access is done in
buckets using the remainder of the division of the key hash_code by
capacity . In order to try to avoid clashes, capacity is always a
prime number (selected using HASH_TABLE_SIZE).
| |
count ] (see item
and valid_index for example) may be saved in cache_user otherwise
-1 to indicate that the cache is not active. When the cache is
active, the corresponding index in buckets is save in
cache_buckets and the corresponding node in cache_node .
| |
cache_user is not -1.
| |
cache_user is not -1.
| |
| |
| |
buckets storage area.
| |
count of stored elements).
Number of available indices.See also is_empty , lower , upper .
| |
| |
| |
| |
| |
| |
See also count .
|
Adding and removing: | |
add feature is actually using is_equal, you may consider
to use fast_add for expanded objects as well while trying to get
the very best performances.
| |
add , but uses basic = for comparison.
| |
| |
remove , but uses basic = for comparison.
| |
| |
is_empty is True after that call).
If possible, the actual implementation is supposed to keep
its internal storage area in order to refill Current in
an efficient way.See also clear_count_and_capacity to select the most appropriate.
| |
is_empty is True after that call).
If possible, the actual implementation is supposed to release
its internal storage area for this memory to be used by other objects.See also clear_count to select the most appropriate.
|
Looking and searching: | |
fast_has for expanded objects as well while trying to get the very
best performances.
| |
See also has when dealing with reference types.
| |
| |
|
To provide iterating facilities: | |
See also lower , upper , valid_index.SETs are intrinsically unordered, so there is no guarantee that item (i) after performing an add or remove operation is related
in any way to item (i) before that operation.
Item at the corresponding index i.See also lower , upper , valid_index.
| |
See also upper , valid_index, item .
| |
See also lower , valid_index, item .
| |
first item.See also last , item .SETs are intrinsically unordered, so there is no guarantee that first after performing an add or remove operation is related
in any way to first before that operation.
The very first item.See also last , item .
| |
last item.See also first , item .SETs are intrinsically unordered, so there is no guarantee that last after performing an add or remove operation is related
in any way to last before that operation.
The last item.See also first , item .
|
Mathematical operations: | |
| |
| |
| |
| |
| |
| |
|
Comparison: | |
| |
| |
| |
|
NONE | |
| |
| |
| |
| |
|
Comparison: | |
|
Agents based features: | |
| |
See also for_all , exists .
| |
See also do_all , exists .
| |
See also do_all , for_all .
|
Inherit/Insert Detail |
.../base/collection/hashed_set.li line #14
.../base/collection/low_level/set.li line #15
.../base/collection/low_level/set.li line #17
Constructor Detail |
.../base/collection/hashed_set.li line #49
capacity
of the set is
initialized using the Default_size value. Then, tuning of needed
storage size is done automatically according to usage. If you
are really sure that your set is always really bigger than
Default_size, you may use with_capacity
to save some execution time.
.../base/collection/hashed_set.li line #69
capacity
. Thus, this feature may be used
in place of make
to save some execution time if one is sure that
storage size will rapidly become really bigger than Default_size (if
not sure, simply use make
). Anyway, the initial medium_size value
is just an indication and never a limit for the possible
capacity
. Keep in mind that the capacity
tuning is done
automatically according to usage.
Detail slot |
.../base/collection/hashed_set.li line #18
.../base/collection/hashed_set.li line #23
buckets
storage area is the primary hash table of capacity
elements. To search some element, the first access is done in
buckets
using the remainder of the division of the key hash_code by
capacity
. In order to try to avoid clashes, capacity
is always a
prime number (selected using HASH_TABLE_SIZE).
.../base/collection/hashed_set.li line #34
count
] (see item
and valid_index for example) may be saved in cache_user
otherwise
-1 to indicate that the cache is not active. When the cache is
active, the corresponding index in buckets
is save in
cache_buckets
and the corresponding node in cache_node
.
.../base/collection/hashed_set.li line #41
cache_user
is not -1.
.../base/collection/hashed_set.li line #44
cache_user
is not -1.
.../base/collection/hashed_set.li line #61
.../base/collection/hashed_set.li line #85
.../base/collection/hashed_set.li line #106
buckets
storage area.
.../base/collection/hashed_set.li line #108
count
of stored elements).
Number of available indices.is_empty
, lower
, upper
.
.../base/collection/hashed_set.li line #452
.../base/collection/hashed_set.li line #467
.../base/collection/hashed_set.li line #500
.../base/collection/hashed_set.li line #516
.../base/collection/hashed_set.li line #545
.../base/collection/low_level/set.li line #31
count
.
Adding and removing: |
.../base/collection/hashed_set.li line #114
add
feature is actually using is_equal, you may consider
to use fast_add
for expanded objects as well while trying to get
the very best performances.
.../base/collection/hashed_set.li line #138
add
, but uses basic = for comparison.
.../base/collection/hashed_set.li line #162
.../base/collection/hashed_set.li line #192
remove
, but uses basic = for comparison.
.../base/collection/hashed_set.li line #222
.../base/collection/low_level/set.li line #102
is_empty
is True after that call).
If possible, the actual implementation is supposed to keep
its internal storage area in order to refill Current in
an efficient way.clear_count_and_capacity
to select the most appropriate.
.../base/collection/low_level/set.li line #116
is_empty
is True after that call).
If possible, the actual implementation is supposed to release
its internal storage area for this memory to be used by other objects.clear_count
to select the most appropriate.
Looking and searching: |
.../base/collection/hashed_set.li line #237
fast_has
for expanded objects as well while trying to get the very
best performances.
.../base/collection/hashed_set.li line #250
has
when dealing with reference types.
.../base/collection/hashed_set.li line #263
.../base/collection/hashed_set.li line #279
To provide iterating facilities: |
.../base/collection/hashed_set.li line #299
lower
, upper
, valid_index.item
(i) after performing an add
or remove
operation is related
in any way to item
(i) before that operation.
Item at the corresponding index i.lower
, upper
, valid_index.
.../base/collection/low_level/set.li line #183
upper
, valid_index, item
.
.../base/collection/low_level/set.li line #185
lower
, valid_index, item
.
.../base/collection/low_level/set.li line #208
first
item.last
, item
.first
after performing an add
or remove
operation is related
in any way to first
before that operation.
The very first
item.last
, item
.
.../base/collection/low_level/set.li line #217
last
item.first
, item
.last
after performing an add
or remove
operation is related
in any way to last
before that operation.
The last
item.first
, item
.
Mathematical operations: |
.../base/collection/hashed_set.li line #310
.../base/collection/hashed_set.li line #344
.../base/collection/hashed_set.li line #360
.../base/collection/low_level/set.li line #272
.../base/collection/low_level/set.li line #309
.../base/collection/low_level/set.li line #330
.../base/collection/low_level/set.li line #367
Comparison: |
.../base/collection/hashed_set.li line #580
.../base/collection/hashed_set.li line #605
.../base/collection/hashed_set.li line #636
.../base/collection/hashed_set.li line #661
NONE |
.../base/collection/hashed_set.li line #681
.../base/collection/hashed_set.li line #699
.../base/collection/hashed_set.li line #716
.../base/collection/hashed_set.li line #733
.../base/collection/hashed_set.li line #750
Comparison: |
.../base/collection/low_level/set.li line #440
Agents based features: |
.../base/collection/low_level/set.li line #529
.../base/collection/low_level/set.li line #531
for_all
, exists
.
.../base/collection/low_level/set.li line #544
do_all
, exists
.
.../base/collection/low_level/set.li line #560
do_all
, for_all
.