Remove JSScript::Create wrapper
Categories
(Core :: JavaScript Engine, task, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox76 | --- | fixed |
People
(Reporter: caroline, Assigned: caroline)
References
Details
Attachments
(3 files)
Since hideScriptFromDebugger flag was removed the JSScript::Create wrapper can be removed.
| Assignee | ||
Comment 1•5 years ago
|
||
Updated•5 years ago
|
Comment 2•5 years ago
|
||
We might as well go further here. Let's try to move JSScript::New to BaseScript and then have BaseScript::CreateRawLazy use the new BaseScript::New so we have a single source of allocation. The places that previously used JSScript::Create can use the BaseScript::New directly, and the places that make lazy scripts can continue using CreateLazy/CreateRawLazy for now.
PRobably will need to fix the argument ordering to be consistent everywhere too.
Comment 3•5 years ago
•
|
||
EDIT: Ignore this comment. I was looking at an old tree... Comment 2 stands.
Actually.. maybe we should leave JSScript::Create as a wrapper around BaseScript::New for now since it also has the immutableFlags argument.
| Assignee | ||
Comment 4•5 years ago
|
||
Depends on D68882
| Assignee | ||
Comment 5•5 years ago
|
||
Depends on D69148
Comment 7•5 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/43d1a93d10cb
https://hg.mozilla.org/mozilla-central/rev/8de231e97e58
https://hg.mozilla.org/mozilla-central/rev/46cab189d719
| Assignee | ||
Comment 8•5 years ago
|
||
Because JSScript::Create returns a JSScript we cannot call BaseScript::New directly, It is still necessary to keep JSScript::Create around to do a static cast of the BaseScript.
Description
•