It doesn't seem to have any dependency on libuv nor on this core, I guess it should not be included in the library, as it could be distributed separately without any problems.
Having one more component means one more pain point for the people who will need to support it through all life-cycle of the stable release. Cheers, Fedor. On Sun, May 18, 2014 at 3:05 PM, Andrius Bentkus <[email protected]>wrote: > However, there is, as far as I can tell, no primitive for communication >> with some other thread(s) from the event loop thread. >> >> Isn't it just an async_t for every loop? >> >> I implemented it in LibuvSharp this way. I gave every loop a personal >> async_t which basically dequeues a callback and executes it. >> > -- > You received this message because you are subscribed to the Google Groups > "libuv" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/libuv. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
