Closed
Bug 1098109
Opened 10 years ago
Closed 9 years ago
add NS_NewRunnableFunction (or similar) so folks stop posting chromium tasks
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: froydnj, Unassigned)
Details
bent pointed this out to me on IRC today:
http://mxr.mozilla.org/mozilla-central/search?string=newrunnablefunction
There's no reason the Gecko places in the above query should be using the chromium message loop instead of the XPCOM one. We just don't provide a sufficient number of pieces.
It'd be a lot easier to do this with variadic templates, of course, but maybe a small, fixed number of templates will encourage people to not pass a million parameters to their functions.
Comment 1•10 years ago
|
||
See https://bugzilla.mozilla.org/show_bug.cgi?id=622728#c21 for my major concern: this should us explicit templates, not inferred.
Comment 2•10 years ago
|
||
Bug 1152753 might make this bug unnecessary.
![]() |
Reporter | |
Comment 3•9 years ago
|
||
The chromium message loop now handles runnables, not tasks.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•