Closed
Bug 1095308
Opened 10 years ago
Closed 10 years ago
Remove some compileAndGo checks from frontend::CompileScript
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla36
People
(Reporter: bzbarsky, Assigned: bzbarsky)
References
Details
Attachments
(1 file)
2.36 KB,
patch
|
luke
:
review+
|
Details | Diff | Splinter Review |
We have: 235 MOZ_ASSERT_IF(evalCaller, options.compileAndGo); and then later in the function: 278 bool savedCallerFun = options.compileAndGo && 279 evalCaller && evalCaller->functionOrCallerFunction(); and 315 if (options.compileAndGo && evalCaller && evalCaller->functionOrCallerFunction()) { so I claim those options.compileAndGo checks after the assert are redundant. At least if we trust the assert.
Assignee | ||
Comment 1•10 years ago
|
||
Attachment #8518700 -
Flags: review?(luke)
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → bzbarsky
Status: NEW → ASSIGNED
Updated•10 years ago
|
Attachment #8518700 -
Flags: review?(luke) → review+
Assignee | ||
Comment 2•10 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/6b1e31309483
Target Milestone: --- → mozilla36
https://hg.mozilla.org/mozilla-central/rev/6b1e31309483
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•