Move JS::ForOfIterator to its own header

RESOLVED FIXED in Firefox 68

Status

()

enhancement
P3
minor
RESOLVED FIXED
5 months ago
5 months ago

People

(Reporter: Waldo, Assigned: Waldo)

Tracking

Trunk
mozilla68
Points:
---

Firefox Tracking Flags

(firefox68 fixed)

Details

Attachments

(1 attachment)

It's a small bit of functionality that wouldn't hurt to be in its own header. Existing users seem to generally depend on additional stuff from jsapi.h, so we can't actually prune that #include from any users, but every user having a smaller jsapi.h to #include is a good thing for sure.

Priority: -- → P3
Pushed by jwalden@mit.edu:
https://hg.mozilla.org/integration/autoland/rev/8e4aef2f75ac
Move JS::ForOfIterator to its own header.  r=arai,bzbarsky
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
Pushed by jwalden@mit.edu:
https://hg.mozilla.org/integration/mozilla-inbound/rev/596886805d4e
Forcibly generate Rust bindings for the JS::RootedValue typedef now that it happens the Rust bindings never themselves use the typedef.  r=bustage
https://hg.mozilla.org/projects/ash/rev/8e4aef2f75acf7fa4e1512ce94c79a4e32f2ca5f
Bug 1537536 - Move JS::ForOfIterator to its own header.  r=arai,bzbarsky

https://hg.mozilla.org/projects/ash/rev/596886805d4ea444c892651be2939360be3561df
Bug 1537536 - Forcibly generate Rust bindings for the JS::RootedValue typedef now that it happens the Rust bindings never themselves use the typedef.  r=bustage
You need to log in before you can comment on or make changes to this bug.