Const equivalents of many [bytemuck
] functions,
and additional functionality.
constmuck
uses bytemuck
's traits,
any type that implements those traits can be used with the
relevant functions from this crate.
The *_alt
functions aren't exactly equivalent to the bytemuck
ones,
each one describes how it's different.
This crate avoids requiring (unstable as of 2021) trait bounds in const fn
s
by using marker types to require that a trait is implemented.
These examples use bytemuck's derives to show how users don't need to
write unsafe
to use this crate,
and use the [konst
] crate to make writing the const functions easier.
This example demonstrates constructing an enum from its representation.
```rust
use constmuck::{Contiguous, infer};
use konst::{array, try_opt};
fn main() { const COLORS: Option<[Color; 5]> = Color::fromarray([3, 4, 1, 0, 2]); asserteq!( COLORS, Some([Color::White, Color::Black, Color::Blue, Color::Red, Color::Green]), );
const NONE_COLORS: Option<[Color; 4]> = Color::from_array([1, 2, 3, 5]);
assert_eq!(NONE_COLORS, None);
}
pub enum Color { Red = 0, Blue, Green, White, Black, }
impl Color {
pub const fn fromint(n: u8) -> Optiontry_opt
returns from from_array
on None
,
// because konst::array::map
allows the passed-in expression
// to return from the surrounding named function.
Some(array::map!(input, |n| try
```
This example demonstrates a type that wraps a [T]
, constructed by reference.
```rust
use constmuck::TransparentWrapper; use constmuck::IsTW;
fn main() {
const SLICE: &[u32] = &[3, 5, 8, 13, 21];
const WRAPPER: &SliceWrapper
const SUM: u64 = WRAPPER.sum();
assert_eq!(SUM, 50);
const FIRST_EVEN: Option<(usize, u32)> = WRAPPER.find_first_even();
assert_eq!(FIRST_EVEN, Some((2, 8)));
}
pub struct SliceWrapper
implconstmuck
allows safely defining this function as a const fn
pub const fn new(reff: &[T]) -> &Self {
constmuck::wrapper::wrap_ref!(reff, IsTW!())
}
}
impl SliceWrapper
}
```
Additional checks are enabled in debug builds,
all of which cause panics when it'd have otherwise been Undefined Behavior
(caused by unsound unsafe impl
s or calling unsafe
constructor functions),
which means that there is a bug in some unsafe code somewhere.
The precise checks are left unspecified so that they can change at any time.
These checks are disabled by default in release builds, to enable them you can use this in your Cargo.toml:
toml
[profile.release.package.constmuck]
debug-assertions = true
These are the features of this crate:
"derive"
(disabled by default):
Enables bytemuck
's "derive"
feature and reexports its derives.
"rust_latest_stable"
(disabled by default):
Enables all items and functionality that requires stable Rust versions after 1.56.0.
Currently doesn't enable any other feature.
"rust_1_57"
(disabled by default, requires Rust 1.57.0):
Causes this crate to use the const_panic
dependency,
to improve the quality of panic messages.
constmuck
is #![no_std]
, it can be used anywhere Rust can be used.
constmuck
requires Rust 1.56.0, because it uses transmute inside const fns.
You can use the "rust_latest_stable"
crate feature to get
all items and functionality that requires stable Rust versions after 1.56.0.
1.1.0
: Add mutable equivalents of reference/slice methods.
This will require adding an opt-in feature.