| ... | ... | @@ -814,7 +814,7 @@ |
| 814 | 814 | <p> |
| 815 | 815 | A destructuring expression may only appear within a block (i.e. not at {#link|Namespace#} scope). |
| 816 | 816 | The left hand side of the assignment must consist of a comma separated list, |
| 817 | | each element of which may be either an lvalue (for instance, an existing `var`) or a variable declaration: |
| 817 | each element of which may be either an lvalue (for instance, an existing {#syntax#}var{#endsyntax#}) or a variable declaration: |
| 818 | 818 | </p> |
| 819 | 819 | {#code|destructuring_mixed.zig#} |
| 820 | 820 | |
| ... | ... | @@ -1917,7 +1917,7 @@ or |
| 1917 | 1917 | </p> |
| 1918 | 1918 | <p> |
| 1919 | 1919 | Vectors generally support the same builtin operators as their underlying base types. |
| 1920 | | The only exception to this is the keywords `and` and `or` on vectors of bools, since |
| 1920 | The only exception to this is the keywords {#syntax#}and{#endsyntax#} and {#syntax#}or{#endsyntax#} on vectors of bools, since |
| 1921 | 1921 | these operators affect control flow, which is not allowed for vectors. |
| 1922 | 1922 | All other operations are performed element-wise, and return a vector of the same length |
| 1923 | 1923 | as the input vectors. This includes: |