E2 Lambda timer scope issues

[unknao]

@name  
@strict
@trigger none

propSpawnUndo(0)
let E1 = propSpawn("models/props_junk/CinderBlock01a.mdl", entity():toWorld(vec(30, 0, 30)), ang(), 1)
let E2 = propSpawn("models/props_junk/CinderBlock01a.mdl", entity():toWorld(vec(0, 0, 30)), ang(), 1)
let E3 = propSpawn("models/props_junk/CinderBlock01a.mdl", entity():toWorld(vec(-30, 0, 30)), ang(), 1)
const A = array(E1, E2, E3)

foreach(_:number, Ent:entity = A){
    local E = Ent
    print("test_initial_" + E:id())
    timer("test_result" + E:id(), 1, 1, function(){
        print("test_result" + E:id())
        E:setPos(E:pos() + vec(0, 0, 10))
    })
}
printTable(getTimers())

This E2 will error because it tries to move the E3 entity 3 times instead of moving all of them once

[unknao]

@strict

for(I = 1, 9){
    timer(1, function(){
        print(I)
    })
}

Actually this is a better example, as this prints 9 9 times

[Denneisk]

Loops share the same scope for their bodies instead of creating a new scope each iteration. Changing this would be a performance decrease on all loop performance. You can mitigate this issue by creating a new scope manually such as with if(1) { ... }, or by using a function.

for(I = 1, 9) {
    if(1) {
        let X = I
        timer(1, function() {
            print(X)
        })
    }
}

[Vurv78]

I feel like people will definitely encounter this case so a scope being created per iteration might be needed. Potential half measure is if this only done as long as a function was created inside.