#internal #const #functions #unstable #implementation #detail


internal implementation detail of constmuck, all of this is unstable

4 releases (2 breaking)

Uses new Rust 2021

0.3.0 Oct 26, 2021
0.2.0 Oct 9, 2021
0.1.1 Sep 16, 2021
0.1.0 Sep 14, 2021
Download history 34/week @ 2021-09-14 347/week @ 2021-09-21 803/week @ 2021-09-28 1156/week @ 2021-10-05 658/week @ 2021-10-12 214/week @ 2021-10-19 404/week @ 2021-10-26 726/week @ 2021-11-02 425/week @ 2021-11-09 46/week @ 2021-11-16 18/week @ 2021-11-23

1,319 downloads per month
Used in constmuck

Zlib license

203 lines

Rust crates-io api-docs

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 fns 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.

use constmuck::{Contiguous, infer};

use konst::{array, try_opt};

fn main() {
    const COLORS: Option<[Color; 5]> = Color::from_array([3, 4, 1, 0, 2]);
        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);

#[derive(Debug, PartialEq, Eq, Contiguous, Copy, Clone)]
pub enum Color {
    Red = 0,

impl Color {
    pub const fn from_int(n: u8) -> Option<Self> {
        constmuck::contiguous::from_u8(n, infer!())
    pub const fn from_array<const N: usize>(input: [u8; N]) -> Option<[Self; N]> {
        // `try_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_opt!(Self::from_int(n))))


This example demonstrates a type that wraps a [T], constructed by reference.

use constmuck::TransparentWrapper;
use constmuck::IsTW;

fn main() {
    const SLICE: &[u32] = &[3, 5, 8, 13, 21];
    const WRAPPER: &SliceWrapper<u32> = SliceWrapper::new(SLICE);

    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)));

#[derive(Debug, PartialEq, Eq, TransparentWrapper)]
pub struct SliceWrapper<T>(pub [T]);

impl<T> SliceWrapper<T> {
    // Using `constmuck` allows safely defining this function as a `const fn`
    pub const fn new(reff: &[T]) -> &Self {
        constmuck::wrapper::wrap_ref!(reff, IsTW!())

impl SliceWrapper<u32> {
    pub const fn sum(&self) -> u64 {
        let mut sum = 0;
        konst::for_range!{i in 0..self.0.len() =>
            sum += self.0[i] as u64;
    pub const fn find_first_even(&self) -> Option<(usize, u32)> {
        konst::for_range!{i in 0..self.0.len() =>
            if self.0[i] % 2 == 0 {
                return Some((i, self.0[i]));

Additional checks

Additional checks are enabled in debug builds, all of which cause panics when it'd have otherwise been Undefined Behavior (caused by unsound unsafe impls 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:

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.

No-std support

constmuck is #![no_std], it can be used anywhere Rust can be used.

Minimum Supported Rust Version

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.