Assigned value is discarded when exiting an inner scope

ask {
    let a = 2

    let c = 'Hello'
    
    if(a < 5) {
        c = '!'
    }
    
    return c
}

returns Hello instead of !

[YonatanKra]

@mhagmajer I dug a little into the runner. It seems like that c = '!' redeclares c with a let. When running @czerwinskilukasz1 's test, I get this object:

[
  {
    "name": "let",
    "params": [
      "b",
      4
    ]
  }
]

In the statements inside fun.ts compute method. Since it is a scoped let statement, it is, well… scoped 😃

It seems like the scope is lost when fragments.ts calls fun.compute on a block.

[mhagmajer]

@YonatanKra I think we should throw a runtime error on when someone attempt to assign value to a undeclared variable. It’s the same like trying to read an undeclared variable - we throw in that case already