jstrong
/
const-crc32
1
Fork 1
Code Issues Pull Requests Projects Releases 2 Wiki Activity
A `const fn` implementation of the crc32 checksum algorithm.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
4 Commits
2 Branches
4 Tags
44 KiB
 
Tree: e765ab544a
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'e765ab544a'
${ noResults }
Jonathan Strong e765ab544a
remove const_eval_limit increase except for cfg(test), which needs it 		2 years ago
src remove const_eval_limit increase except for cfg(test), which needs it 2 years ago
.gitignore initial commit 2 years ago
Cargo.toml remove const_eval_limit increase except for cfg(test), which needs it 2 years ago
LICENSE initial commit 2 years ago
README.md remove const_eval_limit increase except for cfg(test), which needs it 2 years ago

README.md

const-crc32

A const fn crc32 checksum implementation.

Examples

const BYTES: &[u8] = "The quick brown fox jumps over the lazy dog".as_bytes();
const CKSUM: u32 = const_crc32::crc32(BYTES);
assert_eq!(CKSUM, 0x414fa339_u32);

Usage

This is a naive implementation that should be expected to have poor performance if used on dynamic data at runtime. Usage should generally be restricted to declaring const variables based on static or const data available at build time.

#[const_eval_limit]

You may need to increase the crate-wide const_eval_limit setting to use const_crc32 for larger byte slices.

Increating const_eval_limit requires the nightly-only #![feature(const_eval_limit)].

Previously, this crate set the limit itself, however, as of the 2022-10-30 nightly, the value set in const_crc32 does not increase the limit for crates which use the library.

Compile time for const data around 100k is less than 1s.