Move XPCOMUtils.defineLazy/declareLazy to ChromeUtils
Categories
(Core :: XPConnect, task)
Tracking
()
People
(Reporter: standard8, Assigned: standard8)
References
(Blocks 1 open bug)
Details
Attachments
(5 files)
We originally added XPCOMUtils.defineLazy/declareLazy in bug 1945464 as a way of prototyping them and testing out their use.
We are starting to use them in various places to aid with TypeScript integration, and hence we are having to re-include XPCOMUtils in various places.
In the review of the patches, it was suggested that we should move these implementations to C++, i.e. via ChromeUtils, to be more efficient.
| Assignee | ||
Comment 1•2 months ago
|
||
| Assignee | ||
Comment 2•2 months ago
|
||
| Assignee | ||
Comment 3•2 months ago
|
||
| Assignee | ||
Comment 4•2 months ago
|
||
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Updated•1 month ago
|
Updated•1 month ago
|
Updated•1 month ago
|
| Assignee | ||
Comment 5•12 days ago
|
||
Exploration of using webidl types as much as possible in the lazy preference getters. We still can't transition more to the webidl, as the lazy getters are functions that are injected onto JavaScript objects.
If we want to go ahead with this, then I'll fold it into D300779 before landing. I've kept it separate for now in case we don't want to go this far.
Description
•