diff options
| author | Oleksandr Babak <alexanderbabak@proton.me> | 2023-06-26 18:24:17 +0200 |
|---|---|---|
| committer | Tshepang Mbambo <tshepang@gmail.com> | 2023-06-26 18:34:26 +0200 |
| commit | 4a7ca020a99964efce1a4b9dd93f3bc1fa101fc6 (patch) | |
| tree | 272468b629dc2607f6f72de02d3fe34c70da39ba /src/doc/rustc-dev-guide | |
| parent | 14717f41263c5ec9de0d8f20d2b9b458a5a1b9eb (diff) | |
| download | rust-4a7ca020a99964efce1a4b9dd93f3bc1fa101fc6.tar.gz rust-4a7ca020a99964efce1a4b9dd93f3bc1fa101fc6.zip | |
fix_typo
Diffstat (limited to 'src/doc/rustc-dev-guide')
| -rw-r--r-- | src/doc/rustc-dev-guide/src/const-eval.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/doc/rustc-dev-guide/src/const-eval.md b/src/doc/rustc-dev-guide/src/const-eval.md index a7b1c896333..6d301823be5 100644 --- a/src/doc/rustc-dev-guide/src/const-eval.md +++ b/src/doc/rustc-dev-guide/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). |