-
• #3
which apparently was fixed yesterday (nice!).
Actually this post reminded me that
for
loops should have their own scope, so while this got added yesterday, as of builds right now the code you've got will actually work :)
which apparently was fixed yesterday (nice!).
Actually this post reminded me that for
loops should have their own scope, so while this got added yesterday, as of builds right now the code you've got will actually work :)
I've narrowed down a bug to when I use Esprima's Mangle to shorten variable names (other minification options don't generate the error).
I'm seeing an error in the Bangle emulator when I execute this:
I'm getting this error:
You can see that it changed the loop variable to 'g' , which should still be a local variable, but it clearly affects Bangle's 'g'.
However, if you do any one of the following, the error goes away and the Bangle 'g' is fine:
Just thought I'd share; not sure whether this is an Esprima bug, or an interpreter bug (a "let g=" within a for loop should be its own scope and not interfere with global context?)