Factor out Queue() library? about native-promise-only

[getify]

There's one minor but irreconcilable fact which makes Queue not so "general purpose" itself: the cycle = void 0 part.

That part is critical to run at the end of the scheduling-queue drain, but pulling it out of Queue() means I'd have to create another closure or other binding to make it happen, which is a killer for performance.

Now, that having been said, the "scheduling queue" as its own set of functionality (not a general purpose queue but a managed-cycle special-purpose queue) is possibly something that could be general purpose.

I have this gist which does just that. I don't know if it's really something anyone else cares to use, but in theory they could re-use it.

With respect to actually making a separate thing of it, and then having NPO use that thing, that feels like it might be a little overkill. It would probably add a little bit of wrapper boilerplate size (like an IIFE, etc), and it might slow things down a bit, which would be very counter to the overall goal.

I'm open to suggestions here, but I lean toward: let people use the gist if they care. :)

[smikes]

Seems legit.