typeless 0.1.0

`unsafe` inline type erasure
Documentation
  • Coverage
  • 100%
    12 out of 12 items documented0 out of 11 items with examples
  • Size
  • Source code size: 19.92 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 1.37 MB This is the summed size of all files generated by rustdoc for all configured targets
  • Links
  • Homepage
  • Cyborus04/typeless
    0 0 0
  • crates.io
  • Dependencies
    • —
  • Versions
  • Owners
  • Cyborus04

typeless

unsafe API for type erasure on the stack

Usage

Add the following to your Cargo.toml

[dependencies]
typeless = "0.1"

Storing any value x of type T in TypeErased completely destroys all type data associated with it.

Restrictions

While this erases all type data, leaving only the pure bytes, the compiler still requires 2 things:

  • Size: The size of a TypeErased is not based on the data it contains, but rather a const generic parameter C, effectively a "maximum size" on the types it can contain.

  • Alignment: Until there is a way to define alignment by a const parameter, the alignment of TypeErased is 8 bytes, so anything with an alignment of 8 or less can be contained

Access

Since there is no type data anymore, any access to the inner data is unsafe (except getting the bytes directly)

TypeErased is not Send nor Sync since it can't be known if that's safe

License

This project is licensed under either of

at your option.

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.