diff options
| author | Max <me@mkor.je> | 2024-08-20 15:12:12 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-08-20 15:12:12 +0000 |
| commit | cefca7a7d849bc4136fe314fe59a49b70219dbd7 (patch) | |
| tree | 28818df2035762251c29ba0295a48fab4284eec1 /crates/typst-utils/src/hash.rs | |
| parent | 986d624b3a19df757b1ad05576cc0fb1d78dc2d4 (diff) | |
Fix typos (#4784)
Diffstat (limited to 'crates/typst-utils/src/hash.rs')
| -rw-r--r-- | crates/typst-utils/src/hash.rs | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/crates/typst-utils/src/hash.rs b/crates/typst-utils/src/hash.rs index dabae24c..3dbadbe2 100644 --- a/crates/typst-utils/src/hash.rs +++ b/crates/typst-utils/src/hash.rs @@ -16,8 +16,8 @@ use siphasher::sip128::{Hasher128, SipHasher13}; /// Note that for a value `v` of type `T`, `hash(v)` is not necessarily equal to /// `hash(LazyHash::new(v))`. Writing the precomputed hash into a hasher's /// state produces different output than writing the value's parts directly. -/// However, that seldomly matters as you are typically either dealing with -/// values of type `T` or with values of type `LazyHash<T>`, not a mix of both. +/// However, that seldom matters as you are typically either dealing with values +/// of type `T` or with values of type `LazyHash<T>`, not a mix of both. /// /// # Equality /// Because Typst uses high-quality 128 bit hashes in all places, the risk of a |