@@ -85,7 +85,7 @@ See the {{!examples}examples} to jump right into using this library.
85
85
be extended to store size information in nodes if needed.}
86
86
{li Exposes a common interface ({!type:PatriciaTree.NODE.view}) to allow users to write their own pattern
87
87
matching on the tree structure without depending on the {{!PatriciaTree.NODE}[NODE]} being used.}
88
- {li Additionally, hashconsed versions of heterogeneous/homogeneous maps/sets are
88
+ {li Additionally, hash-consed versions of heterogeneous/homogeneous maps/sets are
89
89
available. These provide constant time equality and comparison, and ensure
90
90
maps/set with the same constants are always physically equal. It comes at the cost
91
91
of a constant overhead in memory usage (at worst, as hash-consing may allow
@@ -210,7 +210,7 @@ Here is a small example of a non-generic map:
210
210
let to_int x = x (* to_int must be injective and fast *)
211
211
end
212
212
]}}
213
- {li Use it to instanciate the map/set functors:
213
+ {li Use it to instantiate the map/set functors:
214
214
{[
215
215
module IMap : PatriciaTree.MAP with type key = int
216
216
= PatriciaTree.MakeMap(IntKey)
@@ -353,7 +353,7 @@ liberty of having a generic type as a key.
353
353
Note the full polymorphic equality, that returns a GADT term {!PatriciaTree.cmp}
354
354
which, when equal ({{!PatriciaTree.Eq}[Eq]}), is a proof of type equality
355
355
between the type parameters.}
356
- {li We can now instanciate our map functor. Note that in the heterogeneous case,
356
+ {li We can now instantiate our map functor. Note that in the heterogeneous case,
357
357
we must also specify the value type (second functor argument) and how it depends
358
358
on the key type (first parameter) and the map type (second parameter).
359
359
Here the value only depends on the type of the key, not that of the map
0 commit comments