Re: [swift-evolution] deployment targets and frameworks

> On Apr 6, 2016, at 1:35 PM, Douglas Gregor > wrote: > > Fortunately, Swift tells you when you get it wrong. It doesn't, though. That's the thing. Consider CloudKit, first available in iOS 8. Does that framework's implementation rely on new,

Re: [swift-evolution] deployment targets and frameworks

On Wed, Apr 6, 2016 at 9:58 AM, Douglas Gregor via swift-evolution < swift-evolution@swift.org> wrote: > > On Apr 5, 2016, at 4:04 PM, Drew Crawford wrote: > > > On Apr 5, 2016, at 12:06 PM, Douglas Gregor wrote: > > I would not want this to be

Re: [swift-evolution] deployment targets and frameworks

> On Apr 5, 2016, at 4:04 PM, Drew Crawford wrote: > > >> On Apr 5, 2016, at 12:06 PM, Douglas Gregor > > wrote: >> >> I would not want this to be implicit behavior: it should be recorded in the >> source with, e.g., >>

Re: [swift-evolution] deployment targets and frameworks

> On Apr 5, 2016, at 12:06 PM, Douglas Gregor wrote: > > I would not want this to be implicit behavior: it should be recorded in the > source with, e.g., > > @availability(iOS: 9.3) import YourCustomFramework > > so that it is clear that the imported declarations are

Re: [swift-evolution] deployment targets and frameworks

> On Apr 4, 2016, at 4:48 PM, Drew Crawford via swift-evolution > wrote: > > Suppose *Apple* ships a framework that is only supported in iOS 9.3. As a > direct consequence, the framework is only #available in iOS 9.3 or later. > > Suppose Jane links this framework

Re: [swift-evolution] deployment targets and frameworks

> On Apr 4, 2016, at 7:01 PM, Jonathan Tang wrote: > > I assume that the @available annotation generated would also work for > watchOS, tvOS, etc. frameworks. Yes > How would it work for non-iOS Swift platforms? I'm not terribly familiar > with how #available

Re: [swift-evolution] deployment targets and frameworks

+1 to this. It's really important for getting a sane third-party library ecosystem working. I assume that the @available annotation generated would also work for watchOS, tvOS, etc. frameworks. How would it work for non-iOS Swift platforms? I'm not terribly familiar with how #available works

[swift-evolution] deployment targets and frameworks

Suppose *Apple* ships a framework that is only supported in iOS 9.3. As a direct consequence, the framework is only #available in iOS 9.3 or later. Suppose Jane links this framework into her iOS application. The deployment target for her application *can be any value*. She sets the framework