type-const 1.1.0

Type-level associated consts
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

[![Crates.io](https://img.shields.io/crates/v/type-const.svg)](https://crates.io/crates/type-const)
[![Documentation](https://docs.rs/type-const/badge.svg)](https://docs.rs/type-const)
[![Rust](https://img.shields.io/badge/rust-1.78.0%2B-blue.svg?maxAge=3600)](https://github.com/rust-lang/type-const)

<!-- cargo-rdme start -->

This crate provides simple utils for passing `const` values around through generics,
in the form of types.

The concept of a type const is expressed through the [`Const`](https://docs.rs/type-const/latest/type_const/trait.Const.html) trait, which holds the type and
the value of the constant.

Passing values that are known at compile time through generics is different from passing
them through arguments, for example:
```rust
const fn array_of_const<C: type_const::Const, const N: usize>() -> [C::Type; N] {
    [C::VALUE; N] // no `Copy` needed!
}
assert_eq!(array_of_const::<type_const::DefaultOf<i32>, 3>(), [0; 3]);
```

This may also be used to write `const` "functions" in traits without the nightly
`const_trait` feature. Note that unlike `const fn`, these can only be evaluated at compile
time.
```rust
trait AddConst<Rhs=Self> {
    type Output;
    type Add<
        LhsC: type_const::Const<Type = Self>,
        RhsC: type_const::Const<Type = Rhs>,
    >: Const<Type = Self::Output>;
}
```

<!-- cargo-rdme end -->