Open
Bug 698566
Opened 13 years ago
Updated 2 years ago
Expose JSPropertyName in JSAPI
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: Waldo, Unassigned)
References
(Blocks 1 open bug)
Details
JS_GetElement and friends do fast stuff for uint32 properties. We need similar fast paths for non-uint32 properties known not to be special. Pretty much every place where we look up a property using a char* could use this if it were available.
Reporter | ||
Comment 1•13 years ago
|
||
Luke and I were talking about how it'd be nice if the string hierarchy were exposed -- to some extent (JSShortAtom or whatever shouldn't be exposed, nor should various other internal-use-only classes) -- in the public API. It'd be the usual shadow-class thing and all, with JSString being a class a single word in size, JSLinearString being a subtype of it, JSFixedString a subtype of that, JSAtom under that, JSPropertyName under that. Each class could have member methods that did the cast to the internal type and forward the op, or worked on shadow fields in the shadow class, or whatever. Probably that would want to happen before this.
Comment 2•3 years ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Assignee: jwalden → nobody
Status: ASSIGNED → NEW
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•