Remove ScriptStencil::HasMemberInitializers flag
Categories
(Core :: JavaScript Engine, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox87 | --- | fixed |
People
(Reporter: tcampbell, Assigned: tcampbell)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
As a follow-up to Bug 1688327, we should consider replacing the ScriptStencil::HasMemberInitializers
flag with an ImmutableScriptFlag. This makes sense now that the member initializer data is part of initial parse.
Additionally, we would be able to relax the member-initializer conditions from all class-constructors to simply ones that need it. This would solve Bug 1622371 regression.
Assignee | ||
Comment 1•4 years ago
|
||
Replace this with ImmutableScriptFlagsEnum::UseMemberInitializers since it
must have a consistent value across initial and delazify parses.
Assignee | ||
Comment 2•4 years ago
|
||
If a scripted class constructor has zero member initializers associated with
it, we now avoid storing and updating MemberInitializers data for it. This
avoids the need allocate PrivateScriptData for lazy class constructors that
have no fields or inner functions which saves memory overhead.
Depends on D102840
Comment 4•4 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/1448619c7edd
https://hg.mozilla.org/mozilla-central/rev/d16ebdaed14f
Description
•