feat(pbs): add Map and read-only Keyval associations
This commit is contained in:
@@ -177,11 +177,12 @@ faults. List itself rejects directly optional elements.
|
||||
|
||||
The shared implementation is independent of List representation.
|
||||
[Linked](sdk-linked-and-cursor.md) uses Cursor<T> for forward and reverse captures.
|
||||
[Set](sdk-set-and-identity.md) produces Cursor<T>; future Map<K,V> uses
|
||||
Cursor<keyval<K,V>>. Set/Map gain no ordering guarantee between captures.
|
||||
[Set](sdk-set-and-identity.md) produces Cursor<T>; Map<K,V> uses
|
||||
Cursor<keyval<K,V>> as specified by [Map/Keyval](sdk-map-and-keyval.md).
|
||||
Set/Map gain no ordering guarantee between captures.
|
||||
A captured keyval association is read-only
|
||||
and does not follow later association replacement; referenced objects stay shared.
|
||||
Map and keyval remain separate deliveries.
|
||||
Map owns entry production and Keyval representation while reusing this protocol.
|
||||
|
||||
For n logical List positions and k present occurrences, capture takes O(n) work
|
||||
and O(k) additional nodes; next follows one link in O(1). Each node costs allocation,
|
||||
|
||||
Reference in New Issue
Block a user