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

-Pierre > On Dec 8, 2015, at 7:34 AM, Joakim Hassila via swift-corelibs-dev > wrote: > > Hi Pierre, > > Thanks for the good explanation, will try to respond inline below: > >> On 7 dec. 2015, at 23:10, Pierre Habouzit >

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

> On Dec 8, 2015, at 9:05 AM, Daniel A. Steffen via swift-corelibs-dev > wrote: > >> >> On Dec 8, 2015, at 6:11, Joakim Hassila wrote: >> >> Hi Daniel, >> >> >>> On 7 dec. 2015, at 23:11, Daniel A. Steffen wrote:

Re: [swift-corelibs-dev] libdispatch build issue

Hi, > On Dec 11, 2015, at 12:17 AM, f-dz-f via swift-corelibs-dev > wrote: > > Hi! I’m unable to build on OS X 10.11 > > Using make: > > ../private/voucher_activity_private.h:493:10: fatal error: 'os/lock_private.h' > file not found > #include >

Re: [swift-corelibs-dev] libdispatch build issue

> On Dec 11, 2015, at 9:02 AM, Philippe Hausler via swift-corelibs-dev > wrote: > > This is only tangentially related: but I was attempting to build dispatch as > well to start work on CFRunLoop and a few other dispatch bound features in > Foundation on linux. I

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

> On Dec 10, 2015, at 1:06 AM, Joakim Hassila via swift-corelibs-dev > wrote: > >> On 8 dec. 2015, at 17:07, Pierre Habouzit wrote: >> >> My point is, adding API to dispatch is not something we do lightly. I’m not >> keen on an interface

Re: [swift-corelibs-dev] Issue understanding libdispatch runloop poking

rms of number of files touched, but small in terms of scope). It'll also allow us to check that it doesn't regress other ports which is always a concern ;) > > On Oct 12, 2017, 9:08 PM -0300, Pierre Habouzit via swift-corelibs-dev > <swift-corelibs-dev@swift.org>, wrote

Re: [swift-corelibs-dev] Issue understanding libdispatch runloop poking

> On Oct 12, 2017, at 7:48 AM, Rogiel Sulzbach wrote: > > I am trying to get libdispatch working on FreeBSD but I am hitting a wall: I > cannot get my head around how the runloop implementation dispatches a event > to the kqueue once a new job is submitted. So far I was able

Re: [swift-corelibs-dev] Issue understanding libdispatch runloop poking

> On Oct 12, 2017, at 4:52 PM, Pierre Habouzit via swift-corelibs-dev > <swift-corelibs-dev@swift.org> wrote: > >> On Oct 12, 2017, at 7:48 AM, Rogiel Sulzbach <rog...@rogiel.com >> <mailto:rog...@rogiel.com>> wrote: >> >> I am trying to

Re: [swift-corelibs-dev] Issue understanding libdispatch runloop poking

to be removed. -Pierre > On Oct 12, 2017, at 4:56 PM, Pierre Habouzit via swift-corelibs-dev > <swift-corelibs-dev@swift.org> wrote: > >> On Oct 12, 2017, at 4:52 PM, Pierre Habouzit via swift-corelibs-dev >> <swift-corelibs-dev@swift.org <mailto:swift-corelibs-dev@swi

Re: [swift-corelibs-dev] DispatchQueue and Threads

> On Dec 22, 2017, at 10:59 AM, Pierre Habouzit via swift-corelibs-dev > <swift-corelibs-dev@swift.org> wrote: > >> On Dec 21, 2017, at 10:57 AM, Geordie J via swift-corelibs-dev >> <swift-corelibs-dev@swift.org <mailto:swift-corelibs-dev@swift.org>>