From 3b1e94144015a9336bfa7f730c99e8fdc35eee9c Mon Sep 17 00:00:00 2001 From: Oli Scherer Date: Tue, 20 Jul 2021 12:59:04 +0200 Subject: [PATCH] Update src/const-safety.md Co-authored-by: Ralf Jung --- src/const-safety.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/const-safety.md b/src/const-safety.md index a9f75b2..8fdbc03 100644 --- a/src/const-safety.md +++ b/src/const-safety.md @@ -73,7 +73,7 @@ is defined as follows: * Integer and floating point types are const-safe if they are a `Scalar::Bits`. This makes sure that we can run `%` and other operations without violating - const safety. In particular, the value must *not* be uninitialized. + const safety. In particular, and just like at run-time, the value must *not* be uninitialized. * References are const-safe if they are `Scalar::Ptr` into allocated memory, and the data stored there is const-safe. (Technically, we would also like to require `&mut` to be unique and the memory behind a `&` to not be mutable unless there is an