Improve nested functions' visibility or order-dependency

[Lantua]

Found it. About the reason why closures (functions) capture variables at call site.

Why is the `{}` syntax called `closure expression` in swift?

It's a bit splitting hairs, but no closure record is formed by the compiler until a call site is seen. While this can be seen as merely an optimization for local functions in isolation, it's really necessary for it to work this way for mutually-recursive local functions to work practically with the reference counting and strict initialization semantics Swift requires. If you have: func outer(x: inout T) { var y = 0 func foo() { print(x) bar() } func bar() { print(y) foo(…