A map from ByteStrings to a. For all the generic functions, note that tries are strict in the Maybe but not in a.

The Monad instance is strange. If a key k1 is a prefix of other keys, then results from binding the value at k1 will override values from longer keys when they collide. If this is useful for anything, or if there's a more sensible instance, I'd be curious to know.

Visualization fuction for debugging.

Returns the longest shared prefix and the two remaining suffixes for a pair of strings.

    s == (\(pre,s',z') -> pre `append` s') (breakMaximalPrefix s z)
    z == (\(pre,s',z') -> pre `append` z') (breakMaximalPrefix s z)

O(1), Construct the empty trie.

O(1), Is the trie empty?

O(1), Construct a singleton trie.

O(n), Get count of elements in trie.

Convert a trie into a list (in key-sorted order) using a function, folding the list as we go.

Convert a trie into a list using a function. Resulting values are in key-sorted order.

Generic function to find a value (if it exists) and the subtrie rooted at the prefix. The first function argument is called if and only if a node is exactly reachable by the query; if no node is exactly reachable the default value is used; if the middle of an arc is reached, the second function argument is used.

This function is intended for internal use. For the public-facing version, see lookupBy in Data.Trie.

Return the subtrie containing all keys beginning with a prefix.

Generic function to alter a trie by one element with a function to resolve conflicts (or non-conflicts).

A variant of alterBy which also allows modifying the sub-trie.

Alter the value associated with a given key. If the key is not present, then the trie is returned unaltered. See alterBy if you are interested in inserting new keys or deleting old keys. Because this function does not need to worry about changing the trie structure, it is somewhat faster than alterBy.

Combine two tries, using a function to resolve collisions. This can only define the space of functions between union and symmetric difference but, with those two, all set operations can be defined (albeit inefficiently).

Generic version of fmap. This function is notably more expensive than fmap or filterMap because we have to reconstruct the keys.

Apply a function to all values, potentially removing them.

A variant of fmap which provides access to the subtrie rooted at each value.

A variant of contextualMap which applies the function strictly.

A contextual variant of filterMap.

A contextual variant of mapBy. Again note that this is expensive since we must reconstruct the keys.