clarify variable scope, as in...

[ldemailly]

can read from any scope but only write in current one

[ldemailly]

f2=func() {
       log("called f2", n) // log output
       n
}
f1=func() { // function
    log("called f1", n) // log output
    n=n-1
    log("n in f1 now", n)
    f2() // still bound to top-level env not this one
 }
n=5
f1()

maybe f2() called into f1() should refer to f2's env not the env it was created in...?

or have some option

or have upvar

or have &

[ldemailly]

it's kind of nice as is, so far, all pure functions that we memoized automatically in #72

might reopen and add & later

[ldemailly]

Ok so while trying to trigger an error when a function parameter is a CONSTANT identifier, I stepped on this again

Decided to do the following (in #102 ) :

The environment when calling into a function body is either:

• Based on the environment when the function was defined (capture), ie previous behavior
  or
• Based on the current environment if the function is the same (ie recursing) [which is itself based on time of definition per above when it's the first call]

Note this only works for direct recursion, a->b->a would use env of a as when defined, not the first a
(which maybe is dicey)