[ASYNC-43] queue-dispatcher should fall back to process.nextTick if setImmediate is not available Created: 07/Dec/13 Updated: 05/May/14
discussion of the differences between setImmediate and nextTick here:
it sounds to me like nextTick should be ok, but I'm not familiar with the design decisions in the current implementation
I'm happy to create a patch - will do that shortly.
|Comment by Travis Vachon [ 07/Dec/13 7:28 PM ]|
patch here: https://github.com/clojure/core.async/pull/40
|Comment by Travis Vachon [ 08/Dec/13 8:52 PM ]|
just the code, not entirely sure how to test this, but have tested manually in the parse.com cloud code environment
|Comment by Travis Vachon [ 10/Dec/13 9:53 AM ]|
add git am able patch
|Comment by Travis Vachon [ 05/Mar/14 5:21 PM ]|
just want to ping this issue - anything else it needs to be mergable? I'm using a core.async fork at the moment and would love to get back on the main line!