Support for indefinitely-long queues. about d3-queue HOT 1 CLOSED

I think this is sufficiently different that you’d want a different class. With queue.await and queue.awaitAll, the allowed call pattern is {defer*, await?} or {defer*, awaitAll?}. With queue.awaitNone, it is the opposite: {awaitNone, defer*}. However, there would be no way to prevent {defer*, awaitNone, defer*}, i.e., to prevent queue.defer calls before queue.awaitNone is called. And in that case, you may have accrued results from deferred tasks, so what do you do (discard the results? throw an error? repeatedly invoke the awaitNone callback with each result?).

Seems like a better approach would to be to specify this mode at the time the queue is constructed, e.g., a d3.queueVoid constructor. (Not a good name…)

This also complicates the implementation quite a bit, since now you need a linked list to store the waiting and active tasks lists, so that you can efficiently discard references to tasks as they complete. I’ve implemented that in the linked-list branch, but it increases the library size somewhat.

I think given the work involved and the non-obvious immediate value of this feature, I’m going to close this request. It might be worth revisiting in the future though!

from d3-queue.