Re: [swift-corelibs-dev] Asynchronous Operations

Thank you everyone for your comments. Adding willChangeValue(forKey:) and didChangeValue(forKey:) to Operation does solve the problem for me. The Swift 3 code I'm porting from macOS to Linux works correctly when I patch Foundation as Brent suggests. I've opened a PR against

Re: [swift-corelibs-dev] Asynchronous Operations

Hm, that’s probably the least bad option we have at the moment. I don’t want to introduce “new” API, as it is unlikely we will be able to remove it when whatever permanent solution comes up. - Tony > On Jan 21, 2017, at 6:09 AM, Brent Royal-Gordon via swift-corelibs-dev >

Re: [swift-corelibs-dev] Asynchronous Operations

> On Jan 20, 2017, at 7:55 AM, Ian Partridge via swift-corelibs-dev > wrote: > > Is there any way that we could support asynchronous operations in > swift-corelibs-foundation, in the absence of KVO? Could we add `willChangeValue(forKey:)` and

Re: [swift-corelibs-dev] Asynchronous Operations

> On Jan 20, 2017, at 7:55 AM, Ian Partridge via swift-corelibs-dev > 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

Re: [swift-corelibs-dev] Asynchronous Operations

> On Jan 20, 2017, at 9:55 AM, Ian Partridge via swift-corelibs-dev > 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

[swift-corelibs-dev] Asynchronous Operations

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: