yggdrasil/discrete_range_map
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

correct the copy bit in the readme

Browse Source
This commit is contained in:
ripytide
2023-12-27 12:58:26 +00:00
parent c2cb70aee7
commit 0c99d3caaf
2 changed files with 12 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+6 -3
View File
@@ -15,11 +15,14 @@ off [`BTreeMap`].
`no_std` is supported and should work with the default features.
## You must implement `Copy`
## `Copy` is partially required
Due to implementation complications with non-`Copy` types the
datastructures currently require both the range type and the points
the ranges are over to be `Copy`.
datastructures currently require both the range type and the points the
ranges are over to be `Copy`. However, the value type used when using
the [`DiscreteRangeMap`] does not have to be `Copy`. In fact the only
required traits on the value type are sometimes `Clone` or `Eq` but only
for some methods so if in doubt check a methods trait bounds.
## Example using an Inclusive-Exclusive range
src/lib.rs
+6 -3
View File
@@ -23,11 +23,14 @@ along with discrete_range_map. If not, see <https://www.gnu.org/licenses/>.
//!
//! `no_std` is supported and should work with the default features.
//!
//! ## You must implement `Copy`
//! ## `Copy` is partially required
//!
//! Due to implementation complications with non-`Copy` types the
//! datastructures currently require both the range type and the points
//! the ranges are over to be `Copy`.
//! datastructures currently require both the range type and the points the
//! ranges are over to be `Copy`. However, the value type used when using
//! the [`DiscreteRangeMap`] does not have to be `Copy`. In fact the only
//! required traits on the value type are sometimes `Clone` or `Eq` but only
//! for some methods so if in doubt check a methods trait bounds.
//!
//! ## Example using an Inclusive-Exclusive range
//!