Closed Bug 571810 Opened 15 years ago Closed 15 years ago

TM: slow arrays don't need special objectops

Categories

(Core :: JavaScript Engine, defect)

Other Branch
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: gal, Assigned: gal)

Details

(Whiteboard: fixed-in-tracemonkey)

Attachments

(1 file)

No description provided.
I think this is a left-over from when slow arrays had a weird enumerator handling that dealt with slowification during iteration.
Attached patch patchSplinter Review
Assignee: general → gal
Attachment #450970 - Flags: review?(mrbkap)
You can also remove slowarray_addProperty(), AFAICT. This will cause merge conflicts for my type-specific arrays patch.
(In reply to comment #3) > You can also remove slowarray_addProperty(), AFAICT. Hmm, no, scratch that, I was mixing this up with js_SlowArrayClass. (Hmm, that's odd that we have some class methods in JSClass and some in JSObjectOps.)
Its a layering. ObjectOps implements object behavior ("the hashtable"), Class observes object behavior ("as you put this in the hashtable, call me first so I might change or observe the value on the fly").
Attachment #450970 - Flags: review?(mrbkap) → review+
Andreas asked and we reconstructed that the only reason slow arrays had custom ops was for custom iteration. So this is a followup to fastiterators, in a sense. /be
Landed for Andreas (I need this for other work, myself): http://hg.mozilla.org/tracemonkey/rev/e6d125e859bf /be
Status: NEW → ASSIGNED
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: fixed-in-tracemonkey
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: