Closed
Bug 1616516
Opened 4 years ago
Closed 4 years ago
Simplify ObjectGroup::defaultNewGroup a bit
Categories
(Core :: JavaScript Engine, task, P2)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla75
Tracking | Status | |
---|---|---|
firefox75 | --- | fixed |
People
(Reporter: jandem, Assigned: jandem)
Details
Attachments
(1 file)
The clasp
argument can be nullptr if there's an associated function, but that was just for unboxed objects. We should change the callers to pass the PlainObject class directly so we can simplify defaultNewGroup
a bit.
Assignee | ||
Updated•4 years ago
|
Flags: needinfo?(jdemooij)
Assignee | ||
Updated•4 years ago
|
Flags: needinfo?(jdemooij)
Assignee | ||
Comment 1•4 years ago
|
||
The nullptr class mechanism was added for unboxed objects: because a group with a
PlainObject class could be mutated into a group with an UnboxedPlainObject class,
if we did a lookup with the PlainObject class we would no longer find the group
in the table.
With unboxed objects gone, a group's class can no longer change so we can (again)
always use a non-nullptr class for the table lookup.
Updated•4 years ago
|
Priority: -- → P2
Pushed by jdemooij@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/acc0c8327c26 Always use non-null clasp argument for ObjectGroup::defaultNewGroup and table lookup. r=iain
Comment 3•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox75:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla75
You need to log in
before you can comment on or make changes to this bug.
Description
•