You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently using SpliteratorIterators backed by our custom iterators. This is a bit wasteful, because it allocates an additional object and in case of MutableTrieMap (and hence Mutable{Entry,Key}Set) we end up wrapping the immutable internal structure with a mutable wrapper for each object.
The second part is important, as it is completely unneeded as spliterators cannot modify state, hence we should be able to just traverse an immutable view of the map.
The text was updated successfully, but these errors were encountered:
@rovarga are the keys ordered? (Skiplist/tree map)
No. A Triemap is akin to a ConcurrentHashMap in this regard.
That having been said, a ConcurrentNavigableMap with O(1) snapshot capability could be built using the approach used for internal organization of TrieMap -- I think :)
We are currently using SpliteratorIterators backed by our custom iterators. This is a bit wasteful, because it allocates an additional object and in case of MutableTrieMap (and hence Mutable{Entry,Key}Set) we end up wrapping the immutable internal structure with a mutable wrapper for each object.
The second part is important, as it is completely unneeded as spliterators cannot modify state, hence we should be able to just traverse an immutable view of the map.
The text was updated successfully, but these errors were encountered: