Closed
Bug 1127121
Opened 10 years ago
Closed 10 years ago
Remove ObjectOps property key type splitting
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
mozilla38
People
(Reporter: jorendorff, Assigned: jorendorff)
Details
Attachments
(1 file)
83.01 KB,
patch
|
bhackett1024
:
review+
|
Details | Diff | Splinter Review |
<jorendorff> Waldo: I wrote the patch to get rid of the property-key-type
splitting in JSObjectOps and it's -520 lines of code
<Waldo> jorendorff: sigh
<Waldo> jorendorff: I think this is the wrong direction to move, and I think we
will readd the distinction eventually, but oh well
<jorendorff> yeah - well, maybe! once proxies and ops are unified we'll have
some sort of framework for fallback/default implementations of methods,
right?
<Waldo> jorendorff: that's the plan, yeah
<jorendorff> but we shouldn't carry around complexity we're not using
<jorendorff> posting the patch now
<Waldo> well, there's complexity and complexity
<Waldo> little bits of surface don't really add complexity IMO
Fair, but even if all it adds is a few hundred lines of code, and no complexity to speak of---code isn't free (said the guy who's about to touch every setProperty signature in the codebase).
Assignee | ||
Comment 1•10 years ago
|
||
Attachment #8556174 -
Flags: review?(bhackett1024)
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → jorendorff
Status: NEW → ASSIGNED
Updated•10 years ago
|
Attachment #8556174 -
Flags: review?(bhackett1024) → review+
Assignee | ||
Comment 2•10 years ago
|
||
Assignee | ||
Comment 3•10 years ago
|
||
Assignee | ||
Comment 4•10 years ago
|
||
First try run had some orange that doesn't reproduce locally. Maybe there was something else buggy in the tree at the time, retrying.
Assignee | ||
Comment 5•10 years ago
|
||
Comment 6•10 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla38
You need to log in
before you can comment on or make changes to this bug.
Description
•