Closed
Bug 1699266
Opened 4 years ago
Closed 3 years ago
[meta] Remove internal uses of JSID_* APIs.
Categories
(Core :: JavaScript Engine, enhancement, P3)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
People
(Reporter: mgaudet, Unassigned)
References
Details
(Keywords: meta)
The JSID_* APIs like
Mostly are more obscure than the underlying JS::PropertyKey methods, and so for now we can remove internal uses of these APIs, and replace them with the appropriate JS::PropertyKey methods
|
Reporter | |
Updated•4 years ago
|
Summary: [META] Remove internal uses of JSID_* APIs. → [meta] Remove internal uses of JSID_* APIs.
|
||
Updated•4 years ago
|
Severity: -- → N/A
Priority: -- → P3
|
||
Updated•4 years ago
|
Flags: needinfo?(post.kadirselcuk)
|
|
||
Updated•4 years ago
|
Flags: needinfo?(post.kadirselcuk) → needinfo?(sdetar)
|
|
||
Updated•4 years ago
|
Flags: needinfo?(mgaudet)
|
|
Reporter | |
Updated•4 years ago
|
Flags: needinfo?(sdetar)
Flags: needinfo?(mgaudet)
|
||
Comment 1•3 years ago
|
||
After bug 1699268 and bug 1705195 land we still have JSID_IS_STRING/JSID_TO_STRING, JSID_IS_INT/JSID_TO_INT and JSID_IS_VOID.
We also have the related APIs like INT_TO_JSID, which is still missing a sensible replacement.
|
||
Comment 2•3 years ago
|
||
This is done now that bug 1754405 has landed.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•