diff options
| author | metagn <metagngn@gmail.com> | 2024-09-09 12:29:30 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-09-09 11:29:30 +0200 |
| commit | a6595e5b49ffa94947a2e5767263f523cd827c44 (patch) | |
| tree | 59d0af7aa0d049257c1d82ef5d554cd5202486ab /tests | |
| parent | 9ff0333a4ccffb253f03fc113d086bbc81b566e9 (diff) | |
| download | Nim-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 'tests')
| -rw-r--r-- | tests/vm/tconstscope1.nim | 5 | ||||
| -rw-r--r-- | tests/vm/tconstscope2.nim | 5 |
2 files changed, 10 insertions, 0 deletions
diff --git a/tests/vm/tconstscope1.nim b/tests/vm/tconstscope1.nim new file mode 100644 index 000000000..41c45a28f --- /dev/null +++ b/tests/vm/tconstscope1.nim @@ -0,0 +1,5 @@ +# issue #5395 + +const a = (var b = 3; b) +echo b #[tt.Error + ^ undeclared identifier: 'b']# diff --git a/tests/vm/tconstscope2.nim b/tests/vm/tconstscope2.nim new file mode 100644 index 000000000..d858e96c2 --- /dev/null +++ b/tests/vm/tconstscope2.nim @@ -0,0 +1,5 @@ +const + a = (var x = 3; x) + # should we allow this? + b = x #[tt.Error + ^ undeclared identifier: 'x']# |