Update Android.bp by running cargo_embargo am: 9d90a1a7fd

Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/bytemuck/+/3095419

Change-Id: Ib0392246cf01db110a0bc842c1bd083e97d91361
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
tree: ca52c2d18b1c1d208e675840bee7796ec6fcc1dc
  1. .cargo/
  2. .github/
  3. src/
  4. tests/
  5. .cargo_vcs_info.json
  6. .gitignore
  7. Android.bp
  8. Cargo.toml
  9. Cargo.toml.orig
  10. cargo_embargo.json
  11. changelog.md
  12. LICENSE-APACHE
  13. LICENSE-MIT
  14. LICENSE-ZLIB
  15. METADATA
  16. MODULE_LICENSE_APACHE2
  17. OWNERS
  18. README.md
  19. rustfmt.toml
README.md

License:Zlib Minimum Rust Version crates.io

bytemuck

A crate for mucking around with piles of bytes.

This crate lets you safely perform “bit cast” operations between data types. That's where you take a value and just reinterpret the bits as being some other type of value, without changing the bits.

  • This is not like the as keyword
  • This is not like the From trait
  • It is most like f32::to_bits, just generalized to let you convert between all sorts of data types.

Here‘s the part you’re more likely to care about: you can do this with slices too!

When a slice is involved it‘s not a direct bitcast. Instead, the cast_slice and cast_slice_mut functions will pull apart a slice’s data and give you a new slice that‘s the same span of memory just viewed as the new type. If the size of the slice’s element changes then the length of the slice you get back will be changed accordingly.

This lets you cast a slice of color values into a slice of u8 and send it to the GPU, or things like that. I‘m sure there’s other examples, but honestly this crate is as popular as it is mostly because of Rust's 3D graphics community wanting to cast slices of different types into byte slices for sending to the GPU. Hi friends! Push those vertices, or whatever it is that you all do.

See Also

While bytemuck is full of unsafe code, I've also started a “sibling crate” called bitfrob, which is where operations that are 100% safe will be added.

Stability

  • The crate is 1.0 and I consider this it to be “basically done”. New features are usually being accepted when other people want to put in the work, but myself I wanna move on to using bytemuck in bigger projects.
  • The default build of the bytemuck crate will continue to work with rustc-1.34 for at least the rest of the 1.y.z versions.
  • Any other cargo features of the crate are not held to the same standard, and may work only on the latest Stable or even only on latest Nightly.

Future Plans: Once the Safe Transmute Project completes and stabilizes (“eventually”) this crate will be updated to use that as the underlying mechanism for transmutation bounds, and a 2.0 version of bytemuck will be released. The hope is for the 1.0 to 2.0 transition to be as seamless as possible, but the future is always uncertain.