A crate for mucking around with piles of bytes
Go to file
2021-02-17 21:46:34 -07:00
.github/workflows pod_collect_to_vec (#50) 2021-01-13 16:49:11 -07:00
derive (cargo-release) start next development iteration 1.0.2-alpha.0 2020-11-27 09:33:20 -07:00
src adjust the code to match the claims of the docs. (#53) 2021-02-17 21:43:32 -07:00
tests Prevent try_zeroed_box<T>() from reserving size_of<T>() space on the stack. (#43) 2020-10-21 14:11:09 -06:00
.gitignore update gitignore for bytemuck_derive 2020-08-20 19:45:36 -06:00
Cargo.toml (cargo-release) version 1.5.1 2021-02-17 21:46:34 -07:00
changelog.md changelog. 2021-02-17 21:46:31 -07:00
LICENSE-APACHE Add/rename LICENSE files (#36) 2020-08-31 11:55:43 -06:00
LICENSE-MIT Add/rename LICENSE files (#36) 2020-08-31 11:55:43 -06:00
LICENSE-ZLIB Add/rename LICENSE files (#36) 2020-08-31 11:55:43 -06:00
pedantic.bat base files 2019-09-19 19:09:31 -06:00
README.md readme note 2020-07-25 16:03:30 -06:00
rustfmt.toml Update rustfmt.toml 2020-08-09 14:59:43 -06:00

License:Zlib Minimum Rust Version crates.io docs.rs

bytemuck

A crate for mucking around with piles of bytes.

Extensions

There is experimental support for the Zeroable trait being derived through a proc-macro. I'm not the author of that crate, please file bugs with that crate in the other repo.

Stability

The goal is to stay at 1.y.z until at least the next edition of Rust.

I consider any increase of the Minimum Rust Version to be a semver breaking change, so rustc-1.34 will continue to be supported for at least the rest of the bytemuck-1.y.z series of the crate.

(The secret goal is to get all of this functionality into the standard library some day so that we don't even need to import a crate to do all this fun stuff.)