From 17fe3e948498c50e208047a750f17d6a8d89669b Mon Sep 17 00:00:00 2001 From: Oleksandr Babak Date: Mon, 26 Jun 2023 18:24:17 +0200 Subject: [PATCH] fix_typo --- src/const-eval.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/const-eval.md b/src/const-eval.md index a7b1c896..6d301823 100644 --- a/src/const-eval.md +++ b/src/const-eval.md @@ -56,7 +56,7 @@ The basic rule for being permitted in the type system is that every value must be uniquely represented. In other words: a specific value must only be representable in one specific way. For example: there is only one way to represent an array of two integers as a `ValTree`: -`ValTree::Branch(&[ValTree::Leaf(first_int), ValTree;:Leaf(second_int)])`. +`ValTree::Branch(&[ValTree::Leaf(first_int), ValTree::Leaf(second_int)])`. Even though theoretically a `[u32; 2]` could be encoded in a `u64` and thus just be a `ValTree::Leaf(bits_of_two_u32)`, that is not a legal construction of `ValTree` (and is very complex to do, so it is unlikely anyone is tempted to do so).