Closed
Bug 1804849
Opened 2 years ago
Closed 2 years ago
Make JSContext optional in StringBuffer
Categories
(Core :: JavaScript Engine, task, P1)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
110 Branch
| Tracking | Status | |
|---|---|---|
| firefox110 | --- | fixed |
People
(Reporter: arai, Assigned: arai)
References
Details
Attachments
(1 file)
StringBuffer takes JSContext parameter for handling JSString and also for error reporting,
but JSString handling is not always necessary, and also the error reporting can be handled by the caller.
Making JSContext parameter optional will make it easier to remove JSContext from TokenStream
|
Assignee | |
Comment 1•2 years ago
|
||
Depends on D164334
|
||
Updated•2 years ago
|
Attachment #9307553 -
Attachment description: WIP: Bug 1804849 - Make JSContext* parameter optional in StringBuffer. r?bthrall! → Bug 1804849 - Make JSContext* parameter optional in StringBuffer. r?bthrall!
Pushed by arai_a@mac.com:
https://hg.mozilla.org/integration/autoland/rev/6c9588d29553
Make JSContext* parameter optional in StringBuffer. r=bthrall
|
||
Comment 3•2 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox110:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 110 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•