It's often a requirement to defer a function: in order to complete a Future asynchronously, or to wait for the browser to paint.
Issues 3356 and 2705 can be resolved with an ability to defer a function.
window.setInterval(0, f) (and therefore new Timer(f, 0)) isn't sufficient because it does not invoke the callback on the current or next event loop, but waits at least 4ms (html5 spec) or longer depending on the browser.
IE 10 is adding setImmediate() to handler this and it can be emulated with postMessage.
GWT allows a command to be deferred either till the end of the current event loop, or to the beginning of the next, which follows layout/paint.
This function should live in the same library as Future so that Future can automatically defer Future.complete()
Marked this as blocking #3356.
Added Library-Isolates label.
This comment was originally written by ross.m....@gmail.com
One thing I always liked in GWT was the Scheduler for this:
I'm not saying to take that Java class 'as is' - but the functionality / granularity is great.
This comment was originally written by email@example.com
I think this is actually a duplicate of issue #3260.
Added Library-Isolate label.
Removed Library-Isolates label.
We've added 'scheduleMicrotask' to dart:async to do exactly this. See http://api.dartlang.org/docs/bleeding_edge/dart_async.html#scheduleMicrotask.
Note that some implementations still use Timer.run(...) to implement this, thus still delaying the execution unnecessarily long. This is currently being worked on (there are individual bugs for that).
Added Fixed label.