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 that only works for base queues. Mac OS and iOS code >

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

> 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 that only works for base queues. Mac OS and iOS code > where dispatchy code is pervasive, more than 2 queue deep queues hierarchy is > very c

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: >>> >>> FWIW I’ve updated the macosforge svn repo trunk to match with github

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 > > wrote: >> >> Hi Joakim, Kevin, >> >> [ F

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

> On Dec 8, 2015, at 6:11 AM, Joakim Hassila via swift-corelibs-dev > wrote: > > Hi Daniel, > > >> On 7 dec. 2015, at 23:11, Daniel A. Steffen wrote: >> >> FWIW I’ve updated the macosforge svn repo trunk to match with github >> swift-corelibs-libdispatch trunk (sans the PRs, excecpt for my

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

Hi Pierre, Thanks for the good explanation, will try to respond inline below: On 7 dec. 2015, at 23:10, Pierre Habouzit mailto:phabou...@apple.com>> wrote: Hi Joakim, Kevin, [ Full disclosure, I made that reply in rdar://problem/16436943 and your use case was slightly different IIRC but you’r

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

Hi Daniel, > On 7 dec. 2015, at 23:11, Daniel A. Steffen wrote: > > FWIW I’ve updated the macosforge svn repo trunk to match with github > swift-corelibs-libdispatch trunk (sans the PRs, excecpt for my buildsystem > one), but going forward we are likely going to retire the macosforge > reposi

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

On Mon, Dec 7, 2015, at 04:55 AM, Joakim Hassila via swift-corelibs-dev wrote: > Secondly, we have extended the public libdispatch API internally with > one more flavor of dispatching, let’s call it ‘dispatch_async_inline’ > - the semantics being ‘perform the processing of the work > synchronously

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

Hi Joakim, > On Dec 7, 2015, at 4:55 AM, Joakim Hassila via swift-corelibs-dev > wrote: > > Hi, > > I think (and hope) that this is the proper forum for a few questions wrt to > libdispatch, otherwise any pointers are appreciated. > Yup, you’re in the right place. > We are currently using