Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix error in Readme about feature precedence #110

Merged
merged 1 commit into from
Nov 16, 2023
Merged

Fix error in Readme about feature precedence #110

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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<uxxx>` with e.g. `Crc<Slice16<uxxx>>`. The flavor for `Crc<uxxx>` 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.

Expand Down