#constant #macro #rust

macro const-random-macro

Provides the procedural macro used by const-random

16 releases

0.1.16 Oct 23, 2023
0.1.15 Oct 25, 2022
0.1.13 Dec 5, 2020
0.1.12 Nov 21, 2020
0.1.3 Mar 3, 2019

#2332 in Procedural macros

Download history 631713/week @ 2024-12-14 266622/week @ 2024-12-21 366285/week @ 2024-12-28 680578/week @ 2025-01-04 753406/week @ 2025-01-11 652220/week @ 2025-01-18 736501/week @ 2025-01-25 782523/week @ 2025-02-01 877725/week @ 2025-02-08 807074/week @ 2025-02-15 933081/week @ 2025-02-22 1298720/week @ 2025-03-01 1261653/week @ 2025-03-08 1398377/week @ 2025-03-15 1719712/week @ 2025-03-22 853498/week @ 2025-03-29

5,478,260 downloads per month
Used in 2,345 crates (via const-random)

MIT/Apache

7KB
138 lines

Random constants

This crate provides compile time random number generation. This allows you to insert random constants into your code that will be auto-generated at compile time.

A new value will be generated every time the file is rebuilt. This obviously makes the resulting binary or lib non-deterministic. (See below)

Example

use const_random::const_random  ;
const MY_RANDOM_NUMBER: u32 = const_random!(u32);

This works exactly as through you have called: OsRng.gen::<u32>() at compile time. So for details of the random number generation, see the rand crates documentation.

The following types are supported: u8, i8, u16, i16, u32, i32, u64, i64, u128, i128, usize, isize and [u8; N].

Deterministic builds

Sometimes it is an advantage for build systems to be deterministic. To support this const-random reads the environmental variable CONST_RANDOM_SEED. If this variable is set, it will be used as the seed for the random number generation. Setting the same seed on a build of the same code should result in identical output.

Dependencies

~155–350KB