Remove ReceiverGuard
Categories
(Core :: JavaScript Engine, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox87 | --- | fixed |
People
(Reporter: jandem, Assigned: jandem)
References
Details
Attachments
(1 file)
Nowadays ReceiverGuard
and HeapReceiverGuard
are only used in the property iterator code. There they're always used with native objects, so this means we can just store the Shape*
directly.
This means iterators will be a bit more compact and it makes it easier to remove object groups (bug 1689413).
Assignee | ||
Comment 1•4 years ago
|
||
ReceiverGuard is now only used in the iterator code. There every ReceiverGuard is
created for a native object, in which case ReceiverGuard's group is always nullptr.
This means we can just store the shape directly instead of using ReceiverGuard.
In ExtraStringCount, this removes the |* 2| because we no longer need two words
per guard/shape. This means iterators are now a bit more compact.
Also renames guardKey to shapesHash and uses HashNumber for this instead of uint32_t.
Comment 3•4 years ago
|
||
bugherder |
Description
•