Per scope, the names it binds unconditionally. flowR's static resolution does not always link a use in a
nested function to a binding introduced later in an enclosing scope; the rule consults this as a fallback.
Only unconditional bindings are recorded: one assigned solely inside an if/loop is not guaranteed to
exist, so suppressing an unresolved use of it would hide a real possibly-undefined access.
Per scope, the names it binds unconditionally. flowR's static resolution does not always link a use in a nested function to a binding introduced later in an enclosing scope; the rule consults this as a fallback. Only unconditional bindings are recorded: one assigned solely inside an
if/loop is not guaranteed to exist, so suppressing an unresolved use of it would hide a real possibly-undefined access.