A crate for mucking around with piles of bytes
Go to file
Soveu 52be254e2c
zeroed_slice_box returns Result (#28)
It returns `Result<(), Box>` instead of `Box`
`cargo check` catched it
How did it pass CI?
2020-07-25 15:26:28 -06:00
.github/workflows Update rust.yml 2020-07-25 15:26:01 -06:00
scripts Try to run miri in CI 2020-01-10 11:50:56 -08:00
src zeroed_slice_box returns Result (#28) 2020-07-25 15:26:28 -06:00
tests update offset_of to have 2-arg and 3-arg versions. 2020-07-23 20:21:09 -06:00
.gitignore base files 2019-09-19 19:09:31 -06:00
.travis.yml Update .travis.yml 2020-07-24 07:33:27 -06:00
appveyor.yml 1.34 needed for NonZeroI32 and friends 2019-11-25 19:17:41 -07:00
bors.toml base files 2019-09-19 19:09:31 -06:00
Cargo.toml (cargo-release) version 1.3.0 2020-07-24 20:44:29 -06:00
changelog.md note error updates. 2020-07-24 20:43:32 -06:00
LICENSE-ZLIB.md License change to an equally permissive OSI license 2019-11-25 18:45:54 -07:00
pedantic.bat base files 2019-09-19 19:09:31 -06:00
README.md Update README.md 2020-01-29 01:57:45 -07:00
rustfmt.toml Remove .cast method usage and rustfmt 2019-11-25 18:46:23 -07:00

License:Zlib Minimum Rust Version travis.ci AppVeyor 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.