diff options
author | Tavian Barnes <tavianator@tavianator.com> | 2021-02-24 14:17:12 -0500 |
---|---|---|
committer | Tavian Barnes <tavianator@tavianator.com> | 2021-02-24 14:17:44 -0500 |
commit | 645dad796b4a99de3ab2813b1b4edb4c7f246ba9 (patch) | |
tree | a31fe72a40f4f47115c6cc2310f2deefdd34e3e5 /src/lib.rs | |
parent | 62fe810c118c37b596c5329b9360fec2b33b04b0 (diff) | |
download | acap-645dad796b4a99de3ab2813b1b4edb4c7f246ba9.tar.xz |
docs: Fix a typo in the top-level documentation
Diffstat (limited to 'src/lib.rs')
-rw-r--r-- | src/lib.rs | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -4,8 +4,8 @@ //! //! The notion of distances between points is captured by the [`Proximity`] trait. Its //! [`distance()`] method returns a [`Distance`], from which the actual numerical distance may be -//! retrieved with [`value()`]. These layers of abstraction allow `acap` to work with generically -//! with different distance functions over different types. +//! retrieved with [`value()`]. These layers of abstraction allow `acap` to work generically with +//! different distance functions over different types. //! //! There are no restrictions on the distances computed by a [`Proximity`]. For example, they don't //! have to be symmetric, subadditive, or even positive. Implementations that do have these |