> On Apr 5, 2016, at 12:06 PM, Douglas Gregor <dgre...@apple.com> 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 only available on iOS
> 9.3 or newer.
>
> - Doug
Would you promote using this syntax for the Apple frameworks as well?
A major goal for me is syntax consistency between Apple's and third-party
frameworks. That way the knowledge of how to use one transfers to the other,
and we ensure people with fresh ideas about how to build frameworks are not
burdened with educating application developers about "novel" import syntax.
>From consulting the table
><https://developer.apple.com/library/ios/documentation/Miscellaneous/Conceptual/iPhoneOSTechOverview/iPhoneOSFrameworks/iPhoneOSFrameworks.html>,
> developers with a DT of 7.0 (which is the oldest Swift supports) would need
>to add e.g. @availability(iOS 8.0, *) import CloudKit for a few frameworks,
>but that seems like a pretty easy change.
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution
