Correct. This section is referring more to the NS-side of things. > On Mar 23, 2017, at 1:38 AM, Slava Pestov <spes...@apple.com> wrote: > > >> On Mar 22, 2017, at 10:35 PM, Robert Widmann via swift-evolution >> <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote: >> >> This introduces a source-breaking change that affects consumers of APIs that >> are explicitly taking or vending instances of bridged CF or Objective-C >> types. However, recent importer advances have made APIs like this far less >> numerous. In practice, we expect the source breakage to eludicate places >> where implicit conversions were accidentally being performed behind the >> user's back. >> > > I thought CF APIs were still imported as taking and returning CFArray, etc, > without automatic bridging to Swift collections. Is this no longer the case? > > Slava >
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
