Toplevel 'let' binding can be left permanently uninitialized after an error
brendan at mozilla.org
Tue Sep 30 15:54:28 PDT 2014
David Herman wrote:
> I'm usually less concerned about REPLs, since they can decide for themselves what kind of context they want to execute in -- or even invent new non-standard non-terminals, frankly -- although in this case it's not quite clear what a let declaration*should* do in the REPL. Maybe developer consoles should actually treat `let` the way IMO we should've done for scripts.:)
Agree that nesting is a bad idea for <script> top level scopes.
But a REPL might be the one place nesting works to avoid the issue Jason
raised. Any gotchas there?
More information about the es-discuss