Inherit/Insert Summary | |
| |
| |
No developed. | |
No developed. | |
No developed. |
Constructor Summary | |
|
Slot Summary | |
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.
| |
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.
| |
| |
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.
| |
| |
count of stored elements).
Number of available indices.See also is_empty , lower , upper .
| |
See also count .
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
build_map .
| |
build_map .
| |
| |
| |
|
Adding and removing: | |
| |
remove , but uses basic = for comparison.
| |
| |
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.
Is element e in the set?
| |
See also has when dealing with reference types.
Is element e in the set?
|
To provide iterating facilities: | |
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: | |
| |
| |
| |
|
Duplication. | |
| |
|
Agents based features: | |
| |
See also for_all , exists .
| |
See also do_all , exists .
| |
See also do_all , for_all .
|
Iterating internals: | |
|
Inherit/Insert Detail |
.../base/collection/avl_set.li line #10
.../base/collection/avl_set.li line #12
.../base/collection/low_level/set.li line #15
.../base/collection/low_level/set.li line #17
.../base/collection/low_level/avl_tree.li line #13
Constructor Detail |
.../base/collection/avl_set.li line #93
Detail slot |
.../base/collection/avl_set.li line #16
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/avl_set.li line #22
add
, but uses basic = for comparison.
.../base/collection/avl_set.li line #28
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/avl_set.li line #38
.../base/collection/avl_set.li line #51
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/avl_set.li line #101
.../base/collection/low_level/set.li line #24
count
of stored elements).
Number of available indices.is_empty
, lower
, upper
.
.../base/collection/low_level/set.li line #31
count
.
.../base/collection/low_level/avl_tree.li line #17
.../base/collection/low_level/avl_tree.li line #50
.../base/collection/low_level/avl_tree.li line #52
.../base/collection/low_level/avl_tree.li line #54
.../base/collection/low_level/avl_tree.li line #56
.../base/collection/low_level/avl_tree.li line #61
.../base/collection/low_level/avl_tree.li line #66
.../base/collection/low_level/avl_tree.li line #103
.../base/collection/low_level/avl_tree.li line #140
.../base/collection/low_level/avl_tree.li line #193
.../base/collection/low_level/avl_tree.li line #247
.../base/collection/low_level/avl_tree.li line #292
.../base/collection/low_level/avl_tree.li line #333
.../base/collection/low_level/avl_tree.li line #359
.../base/collection/low_level/avl_tree.li line #417
.../base/collection/low_level/avl_tree.li line #474
.../base/collection/low_level/avl_tree.li line #488
.../base/collection/low_level/avl_tree.li line #499
.../base/collection/low_level/avl_tree.li line #547
build_map
.
.../base/collection/low_level/avl_tree.li line #550
build_map
.
.../base/collection/low_level/avl_tree.li line #556
.../base/collection/low_level/avl_tree.li line #561
.../base/collection/low_level/avl_tree.li line #567
Adding and removing: |
.../base/collection/low_level/set.li line #71
.../base/collection/low_level/set.li line #86
remove
, but uses basic = for comparison.
.../base/collection/low_level/set.li line #100
.../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/low_level/set.li line #133
fast_has
for expanded objects as well while trying to get the very
best performances.
Is element e in the set?
.../base/collection/low_level/set.li line #149
has
when dealing with reference types.
Is element e in the set?
To provide iterating facilities: |
.../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/low_level/set.li line #230
.../base/collection/low_level/set.li line #251
.../base/collection/low_level/set.li line #272
.../base/collection/low_level/set.li line #288
.../base/collection/low_level/set.li line #309
.../base/collection/low_level/set.li line #330
.../base/collection/low_level/set.li line #346
.../base/collection/low_level/set.li line #367
Comparison: |
.../base/collection/low_level/set.li line #387
.../base/collection/low_level/set.li line #411
.../base/collection/low_level/set.li line #440
.../base/collection/low_level/set.li line #469
Duplication. |
.../base/collection/low_level/set.li line #494
.../base/collection/low_level/set.li line #509
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
.
Iterating internals: |
.../base/collection/low_level/avl_tree.li line #532