about summary refs log tree commit diff
path: root/src/libstd/collections
diff options
context:
space:
mode:
authorVal <dgm97@cornell.edu>2018-09-10 09:02:16 -0700
committerGitHub <noreply@github.com>2018-09-10 09:02:16 -0700
commitabe0f027ae23b47dfabeb217aaa56b155d565ae3 (patch)
tree9bd016c0bd7c781d76fd2d4d9e4b33f6ef87177e /src/libstd/collections
parent595345419d12c3ea860151df52f78744a31bafff (diff)
downloadrust-abe0f027ae23b47dfabeb217aaa56b155d565ae3.tar.gz
rust-abe0f027ae23b47dfabeb217aaa56b155d565ae3.zip
fix typos in growth algo description
modified to read "the first table overflows into the second, and the second into the first." plus smaller typos
Diffstat (limited to 'src/libstd/collections')
-rw-r--r--src/libstd/collections/hash/map.rs8
1 files changed, 4 insertions, 4 deletions
diff --git a/src/libstd/collections/hash/map.rs b/src/libstd/collections/hash/map.rs
index 3e54b502234..804d43f4fc6 100644
--- a/src/libstd/collections/hash/map.rs
+++ b/src/libstd/collections/hash/map.rs
@@ -166,14 +166,14 @@ impl DefaultResizePolicy {
 // Our hash generation scheme consists of generating a 64-bit hash and
 // truncating the most significant bits. When moving to the new table, we
 // simply introduce a new bit to the front of the hash. Therefore, if an
-// elements has ideal index i in the old table, it can have one of two ideal
+// element has ideal index i in the old table, it can have one of two ideal
 // locations in the new table. If the new bit is 0, then the new ideal index
 // is i. If the new bit is 1, then the new ideal index is n + i. Intuitively,
 // we are producing two independent tables of size n, and for each element we
 // independently choose which table to insert it into with equal probability.
-// However the rather than wrapping around themselves on overflowing their
-// indexes, the first table overflows into the first, and the first into the
-// second. Visually, our new table will look something like:
+// However, rather than wrapping around themselves on overflowing their
+// indexes, the first table overflows into the second, and the second into the
+// first. Visually, our new table will look something like:
 //
 // [yy_xxx_xxxx_xxx|xx_yyy_yyyy_yyy]
 //