From d7d51fa809fc4880f21676667d07411bee8640af Mon Sep 17 00:00:00 2001 From: Moritz Borcherding Date: Thu, 16 Nov 2023 08:50:54 +0100 Subject: [PATCH] Fix error in Readme about feature precedence The readme had a copy-paste error, where it said "slice16-mem-limit" instead of "no-table-mem-limit" --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index a01ef30..4964970 100644 --- a/README.md +++ b/README.md @@ -58,9 +58,9 @@ See the benchmark section for hints, but do benchmarks on your target hardware t These can be used by substituting `Crc` with e.g. `Crc>`. The flavor for `Crc` is chosen based on three crate features: -* no-table-mem-limit: Takes precedence over "bytewise-mem-limit" and "slice16-mem-limit" -* bytewise-mem-limit: Takes precedence over "slice16-mem-limit" -* slice16-mem-limit: Can be overriden by setting "bytewise-mem-limit" and "slice16-mem-limit" +* no-table-mem-limit: Takes precedence over "bytewise-mem-limit" or "slice16-mem-limit" +* bytewise-mem-limit: Takes precedence over "slice16-mem-limit" and can be overridden by setting "no-table-mem-limit" +* slice16-mem-limit: Can be overridden by setting "bytewise-mem-limit" or "no-table-mem-limit" If no feature is selected, the `Bytewise` flavor is used.