> On Jan 20, 2017, at 9:55 AM, Ian Partridge via swift-corelibs-dev > <swift-corelibs-dev@swift.org> wrote: > > On Darwin, asynchronous usage of Operation is supported via KVO notifications. > > Because KVO is only available on Darwin platforms, swift-corelibs-foundation > currently does not support asychronous Operations, and there is a comment to > that effect: > > https://github.com/apple/swift-corelibs-foundation/blob/6c2afef20330681ec1f8e4e4e3e2664bfd758888/Foundation/NSOperation.swift#L50 > > <https://github.com/apple/swift-corelibs-foundation/blob/6c2afef20330681ec1f8e4e4e3e2664bfd758888/Foundation/NSOperation.swift#L50> > > My understanding is that it's unlikely KVO will arrive on Linux any time > soon, so this leaves us with a problem in Operation. Asynchronous usage of > Operation is an important feature. > > Is there any way that we could support asynchronous operations in > swift-corelibs-foundation, in the absence of KVO? > > Might it be acceptable to add extra temporary public API to enable this?
+ 1. IMO eliminating the dependence of an API like this on KVO would be a good thing regardless of whether KVO is present or not. > > Many thanks, > > -- > Ian Partridge > > _______________________________________________ > swift-corelibs-dev mailing list > swift-corelibs-dev@swift.org > https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
_______________________________________________ swift-corelibs-dev mailing list swift-corelibs-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
