Roms1383
/
const-crc32
forked from jstrong/const-crc32
1
Fork 0
Code Issues Pull Requests Projects Releases 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.
3 Commits
2 Branches
3 Tags
46 KiB
 
Branch: master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
Jonathan Strong 7324963d2b
increase #[const_eval_limit] to avoid compilation errors for larger byte slices 		3 years ago
src increase #[const_eval_limit] to avoid compilation errors for larger byte slices 3 years ago
.gitignore initial commit 3 years ago
Cargo.toml increase #[const_eval_limit] to avoid compilation errors for larger byte slices 3 years ago
LICENSE initial commit 3 years ago
README.md increase #[const_eval_limit] to avoid compilation errors for larger byte slices 3 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]

This crate sets #[const_eval_limit] to 1,000,000,000 to avoid hitting the limit when executing the const fn, which requires #![feature(const_eval_limit)].

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