Closed
Bug 1664363
Opened 4 years ago
Closed 4 years ago
Use JS::CompileAndStartIncrementalEncoding in shell
Categories
(Core :: JavaScript Engine, task, P1)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
82 Branch
Tracking | Status | |
---|---|---|
firefox82 | --- | fixed |
People
(Reporter: arai, Assigned: arai)
References
Details
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
JS::StartIncrementalEncoding
should go away given it receives JSScript
.
the remaining consumer is only JS shell, we should use JS::CompileAndStartIncrementalEncoding
there.
Assignee | ||
Comment 1•4 years ago
|
||
Updated•4 years ago
|
Attachment #9175159 -
Attachment description: Bug 1664363 - Remove JS::StartIncrementalEncoding and use JS::CompileAndStartIncrementalEncoding in shell. r?tcampbell! → Bug 1664363 - Replace JS::DecodeScript + JS::StartIncrementalEncoding with JS::DecodeScriptAndStartIncrementalEncoding. r?tcampbell
Pushed by arai_a@mac.com:
https://hg.mozilla.org/integration/autoland/rev/1703455bfd04
Replace JS::DecodeScript + JS::StartIncrementalEncoding with JS::DecodeScriptAndStartIncrementalEncoding. r=tcampbell
Comment 3•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox82:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 82 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•