Skip to content

Instantly share code, notes, and snippets.

@kmaglione
Created September 17, 2014 22:26
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save kmaglione/f0d97de7cf301ddc6b5a to your computer and use it in GitHub Desktop.
Save kmaglione/f0d97de7cf301ddc6b5a to your computer and use it in GitHub Desktop.
Hello,
As part of recent ES6 compliance efforts, the semantics of the `let`
keyword have changed[1] in a non-backwards-compatible way which
affects one or more of your add-ons. In particular:
1) Variables may no longer be declared more than once in the same
scope using the `let` keyword, and may not be redeclared using the
`let` keyword if they have already been declared using `var`, or as
a function argument, within the same lexical scope.
This means that, as of Firefox 35, none of the following are
acceptable:
function f(foo) {
let foo;
}
{
let foo;
let foo = y;
}
{
let foo;
var foo;
}
2) Variables declared using the `let` keyword may no longer be
referenced before the `let` statement which binds them has executed.
This means that the following will no longer work:
{
x = 4;
let x;
}
switch (2) {
case 1:
let x = 'foo';
case 2:
x = 'bar';
}
You are receiving this email because the following %(addon)s fall
awry of the first class of new restrictions in the following
%(file)s. Note that the second class of errors are only detectable
%during runtime, and may exist in other files or addons.
%(addon_list)s
Thanks,
The Mozilla Add-ons Team
[1] https://bugzil.la/1001090
======================================================================
You are receiving this email because you currently host one or more
add-ons on addons.mozilla.org. It is not possible to opt out of this
type of email while you continue to do so.
Other addons.mozilla.org notification settings can be modified at:
https://addons.mozilla.org/users/edit#acct-notify
======================================================================
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment