Closed
Bug 1313490
Opened 8 years ago
Closed 8 years ago
Remove expression closures from our tests
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla53
Tracking | Status | |
---|---|---|
firefox53 | --- | fixed |
People
(Reporter: evilpie, Assigned: arai)
References
Details
Attachments
(3 files)
77.56 KB,
patch
|
evilpie
:
review+
|
Details | Diff | Splinter Review |
18.39 KB,
patch
|
evilpie
:
review+
|
Details | Diff | Splinter Review |
2.34 KB,
patch
|
mrbkap
:
review+
|
Details | Diff | Splinter Review |
Before we can disable expression closures in Nightly we have to first remove all uses of expression closures from our JS tests. (Of course unless we actually *want* to test expression closures in a test)
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → arai.unmht
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•8 years ago
|
||
Changed to function expression or arrow function in tests that doesn't test parser.
Attachment #8813500 -
Flags: review?(evilpies)
Assignee | ||
Comment 3•8 years ago
|
||
expression closure is used to test warning there. we can use "statement after return" instead.
Attachment #8813504 -
Flags: review?(mrbkap)
Reporter | ||
Comment 4•8 years ago
|
||
Comment on attachment 8813500 [details] [diff] [review] Part 1: Remove unnecessary expression closure from jit-test. Review of attachment 8813500 [details] [diff] [review]: ----------------------------------------------------------------- There a bunch more cases where `return` would be unnecessary, but considering that most tests look like fuzz tests anyway we can just preserve the current behavior more closely. ::: js/src/jit-test/tests/arguments/defaults-destructuring-expression-closure.js @@ +2,5 @@ > + return ( > + assertEq(a, 1), > + assertEq(b, bIs), > + assertEq(c, cIs), > + assertEq(d, dIs) Remove the return and () around the asserts. ::: js/src/jit-test/tests/baseline/bug852801.js @@ -13,5 @@ > for (var i=0; i<lines.length; i++) > print (STATUS + lines[i]); > } > function printBugNumber (num) {} > -function toPrinted(value) That was confusing
Attachment #8813500 -
Flags: review?(evilpies) → review+
Reporter | ||
Updated•8 years ago
|
Attachment #8813501 -
Flags: review?(evilpies) → review+
Updated•8 years ago
|
Attachment #8813504 -
Flags: review?(mrbkap) → review+
Assignee | ||
Comment 5•8 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/8aee096b3c4b3780b5d1a61d814bfe383664e285 Bug 1313490 - Part 1: Remove unnecessary expression closure from jit-test. r=evilpie https://hg.mozilla.org/integration/mozilla-inbound/rev/64a9c8f9d503f56b914566f6943cf084381e96fe Bug 1313490 - Part 2: Remove unnecessary expression closure from jstests. r=evilpie https://hg.mozilla.org/integration/mozilla-inbound/rev/349bfd47d48b4af6eb1b8d8e1485d928e65606aa Bug 1313490 - Part 3: Remove expression closure from dom/. r=mrbkap
Comment 6•8 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/8aee096b3c4b https://hg.mozilla.org/mozilla-central/rev/64a9c8f9d503 https://hg.mozilla.org/mozilla-central/rev/349bfd47d48b
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
status-firefox53:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla53
You need to log in
before you can comment on or make changes to this bug.
Description
•