core.async

queue-dispatcher should fall back to process.nextTick if setImmediate is not available

Details

  • Type: Defect Defect
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:

Description

discussion here:

https://groups.google.com/forum/#!searchin/clojurescript/nextTick/clojurescript/RW1FMv0UoPE/hsMHI4SLKXYJ

discussion of the differences between setImmediate and nextTick here:

http://stackoverflow.com/questions/15349733/setimmediate-vs-nexttick

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.

  1. async_43.patch
    10/Dec/13 9:53 AM
    1 kB
    Travis Vachon
  2. nextTick.patch
    08/Dec/13 8:52 PM
    0.6 kB
    Travis Vachon

Activity

People

Vote (0)
Watch (2)

Dates

  • Created:
    Updated: