Skip to content

Commit f91c680

Browse files
committed
doc fixups
1 parent 7c04b3c commit f91c680

File tree

1 file changed

+3
-3
lines changed
  • src/libcollections/btree

1 file changed

+3
-3
lines changed

src/libcollections/btree/map.rs

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -45,14 +45,14 @@ use ringbuf::RingBuf;
4545
/// searches. However, this does mean that searches will have to do *more* comparisons on average.
4646
/// The precise number of comparisons depends on the node search strategy used. For optimal cache
4747
/// effeciency, one could search the nodes linearly. For optimal comparisons, one could search
48-
/// search the node using binary search. As a compromise, one could also perform a linear search
48+
/// the node using binary search. As a compromise, one could also perform a linear search
4949
/// that initially only checks every i<sup>th</sup> element for some choice of i.
5050
///
5151
/// Currently, our implementation simply performs naive linear search. This provides excellent
5252
/// performance on *small* nodes of elements which are cheap to compare. However in the future we
5353
/// would like to further explore choosing the optimal search strategy based on the choice of B,
5454
/// and possibly other factors. Using linear search, searching for a random element is expected
55-
/// to take O(Blog<sub>B</sub>n) comparisons, which is generally worse than a BST. In practice,
55+
/// to take O(B log<sub>B</sub>n) comparisons, which is generally worse than a BST. In practice,
5656
/// however, performance is excellent. `BTreeMap` is able to readily outperform `TreeMap` under
5757
/// many workloads, and is competetive where it doesn't. BTreeMap also generally *scales* better
5858
/// than TreeMap, making it more appropriate for large datasets.
@@ -68,7 +68,7 @@ use ringbuf::RingBuf;
6868
/// it's possible to force one to occur at every single level of the tree in a single insertion or
6969
/// deletion. In fact, a malicious or otherwise unlucky sequence of insertions and deletions can
7070
/// force this degenerate behaviour to occur on every operation. While the total amount of work
71-
/// done on each operation isn't *catastrophic*, and *is* still bounded by O(Blog<sub>B</sub>n),
71+
/// done on each operation isn't *catastrophic*, and *is* still bounded by O(B log<sub>B</sub>n),
7272
/// it is certainly much slower when it does.
7373
#[deriving(Clone)]
7474
pub struct BTreeMap<K, V> {

0 commit comments

Comments
 (0)