Closed
Bug 1059843
(non-standard-js)
Opened 10 years ago
Closed 7 years ago
Stop using non-standard SpiderMonkey extensions in Thunderbird JS code [meta]
Categories
(Thunderbird :: General, defect)
Thunderbird
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jcranmer, Unassigned)
References
Details
(Keywords: meta)
The things I saw most recently as being investigated for removal:
* Old style generators (yield in non-function*, Iterator)
* for each loops
(Might [x for (x of arr)] instead of [for (x of arr) x] be involved as well?)
Reporter | ||
Comment 1•10 years ago
|
||
Bug 1054630 has a better list of extensions:
* destructuring for-in
* for-each
* legacy generator
* expression closures [I think this is function () x ?]
Updated•10 years ago
|
Alias: non-standard-js
Reporter | ||
Comment 2•10 years ago
|
||
There's also let blocks: <https://dxr.mozilla.org/comm-central/search?q=regexp%3A%22let\s*\%28%22+-path%3Amozilla&case=true>. Interestingly, of the 11 uses, 3 of them seem to be copy-paste clones.
We have a ton of for..in usage with fixIterator(). Do you know how to rewrite that function so it can be used with for..of? Should I file that bug?
Actually it is already the bug 824104. Could you help there?
Reporter | ||
Comment 5•10 years ago
|
||
(In reply to :aceman from comment #3)
> We have a ton of for..in usage with fixIterator(). Do you know how to
> rewrite that function so it can be used with for..of? Should I file that bug?
I have a prototype patch that should make fixIterator simultaneously usable with for..in and for..of.
Updated•10 years ago
|
Keywords: meta
Summary: Stop using non-standard SpiderMonkey extensions in Thunderbird JS code → Stop using non-standard SpiderMonkey extensions in Thunderbird JS code [meta]
Comment 6•7 years ago
|
||
The platform already removed JavaScript versions.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•