summary refs log tree commit diff stats
path: root/doc
diff options
context:
space:
mode:
authormetagn <metagngn@gmail.com>2024-09-09 12:29:30 +0300
committerGitHub <noreply@github.com>2024-09-09 11:29:30 +0200
commita6595e5b49ffa94947a2e5767263f523cd827c44 (patch)
tree59d0af7aa0d049257c1d82ef5d554cd5202486ab /doc
parent9ff0333a4ccffb253f03fc113d086bbc81b566e9 (diff)
downloadNim-a6595e5b49ffa94947a2e5767263f523cd827c44.tar.gz
open new scope for const values (#24084)
fixes #5395

Previously values of `const` statements used the same scope as the
`const` statement itself, meaning variables could be declared inside
them and referred to in other statements in the same block. Now each
`const` value opens its own scope, so any variable declared in the value
of a constant can only be accessed for that constant.

We could change this to open a new scope for the `const` *section*
rather than each constant, so the variables can be used in other
constants, but I'm not sure if this is sound.
Diffstat (limited to 'doc')
-rw-r--r--doc/manual.md9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/manual.md b/doc/manual.md
index 693fb7330..5c36a0a7b 100644
--- a/doc/manual.md
+++ b/doc/manual.md
@@ -3220,6 +3220,15 @@ A const section declares constants whose values are constant expressions:
 
 Once declared, a constant's symbol can be used as a constant expression.
 
+The value part of a constant declaration opens a new scope for each constant,
+so no symbols declared in the constant value are accessible outside of it.
+
+  ```nim
+  const foo = (var a = 1; a)
+  const bar = a # error
+  let baz = a # error
+  ```
+
 See [Constants and Constant Expressions] for details.
 
 Static statement/expression