[swift-corelibs-dev] libdispatch roadmap and api addition proposal

Joakim Hassila Joakim.Hassila at orc-group.com
Tue Dec 8 08:16:28 CST 2015

Hi Tony,

> On 7 dec. 2015, at 20:37, Tony Parker <anthony.parker at apple.com> wrote:
> I think it’s reasonable to continue to depend on libkqueue here where we can. We may have to have some kind of config option to use pure userspace stuff on certain platforms. I’m also open to the idea of getting something with fewer dependencies and lower performance done as an early first step, so we can unblock all of the API above libdispatch that wants to just use queues.

That would make sense - just want to point out that libkqueue and libpwq are separate - the same question posed for libpwq in a separate mail would be relevant for libkqueue as well - would closer integration make sense, or just keep things separate?

>> Our most important goal for year one is to get the core library implementations up to date with where we are on Darwin on platforms like Linux. API changes are not out of the question but we have to make sure they align with that goal. This is the right place to discuss them, though. We’ll be in a much better place to evaluate it when we get dispatch building & running.

Thanks, to complete the bringup of the core libraries makes sense, we’d just want to understand how to approach (the very few) API additions we’ve made - and it’s good its the right forum.




This e-mail is confidential and may contain legally privileged information. It is intended only for the addressees. If you have received this e-mail in error, kindly notify us immediately by telephone or e-mail and delete the message from your system.

More information about the swift-corelibs-dev mailing list