You probably know this better than me: will the compiler always recognize that 
what came from "#import/#include <Cocoa/Cocoa.h>" (not @import Cocoa) is the 
same as what comes from Swift's "import Cocoa"? What about non-module includes?
Are we saying that you can always re-import a module and the last import wins, 
or is that a special case for symbols that come from a C header instead of 
Swift code?
Félix

    On Thursday, July 21, 2016 9:36 AM, Robert Widmann <[email protected]> 
wrote:


import Cocoa hiding (NSWindow)
Done.  This specific case is one of the reasons why imports are file-local.


  
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution

Reply via email to