Error: cannot evaluate at compile time when using var in a static: block inside a proc

[timotheecour]

reduced from a more complex scenario:

template baz*() =
  var i = 0

proc foo2() =
  static:
    when defined(case1):
      # Error: cannot evaluate at compile time:
      var i = 0
    when defined(case2):
      # Error: cannot evaluate at compile time:
      baz()

static:
  when defined(case3):
    # ok
    var i = 0
  when defined(case4):
    # ok
    baz()

maybe related

• {.compileTime.} var doesn't work inside proc [WONTFIX] {.compileTime.} var doesn't work inside proc #8733
• typedesc[T] can't be used at compile time, unlike generics typedesc[T] can't be used at compile time, unlike generics #8486
• Error: cannot evaluate at compile time for typedesc parameters (works for generics) [WONTFIX] Error: cannot evaluate at compile time for typedesc parameters (works for generics) #7596
• static bug static bug #6297

[LemonBoy]

Minimal test case:

proc foo() =
  static:
    var i = 42
    echo i

The problem here is that the static block is "transparent" and the whole body is semanticized as if it were part of the enclosing foo. This means that the compile-time variable i is generated with foo as symbol owner and that makes it impossible for the VM to recognize whether it's a CT variable or not.

The proposed solution is: let's push the outer module as owner.

CC @Araq