- From: Domenic Denicola <notifications@github.com>
- Date: Fri, 10 Apr 2015 09:27:15 -0700
- To: whatwg/streams <streams@noreply.github.com>
Received on Friday, 10 April 2015 16:27:51 UTC
@wanderview given > So I see this as an "async required" problem and not Promise specific. If we could implement this with just callbacks without hitting set time out clamping I think we would see similar results. Maybe a good way to cut out the noise here is to actually test callbacks + a loop (i.e., manually emulate the microtask queue) and compare that to sync read. Then we can see if an ideal fast microtask queue/promise implementation still introduces 7 ms of latency, or if it's just a Firefox-on-mobile optimization issue. --- Reply to this email directly or view it on GitHub: https://github.com/whatwg/streams/issues/320#issuecomment-91608240
Received on Friday, 10 April 2015 16:27:51 UTC