Files
Nim/tests/vm
metagn a6595e5b49 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.
2024-09-09 11:29:30 +02:00
..
2018-08-13 13:02:52 +02:00
2017-07-25 09:28:23 +02:00
2019-02-01 12:12:10 +01:00
2018-08-13 13:02:52 +02:00
2016-08-23 01:10:34 +02:00
2017-02-05 08:51:43 +01:00
2019-09-28 19:50:20 +02:00
2019-08-02 22:59:04 +01:00
2019-05-21 21:31:40 +02:00
2018-12-11 21:23:22 +01:00
2016-10-09 18:02:48 +02:00
2018-06-26 21:25:27 +02:00
2018-10-27 14:10:05 +01:00
2018-08-13 23:16:03 +02:00
2018-11-23 11:58:28 +01:00
2020-12-28 14:13:21 +01:00
2020-11-05 14:00:08 +01:00
2020-12-28 14:13:21 +01:00
2017-07-25 09:28:23 +02:00
2014-03-16 20:42:49 +02:00