On Mar 11, 2015, at 00:25 , Charles Srstka <cocoa...@charlessoft.com> wrote: > > You know, this sounds like a good candidate for a collection contents > annotation, similar to the nullability annotations that were recently added > to Xcode. If there was a way to notate in an Objective-C header that this > method returns an NSArray of NSStrings instead of just an NSArray of > anything, it would make using Objective-C objects from Swift a lot easier.
Running with this idea to an extreme, I could see value in “writing” the OS X 10.11/iOS 9 SDKs in Swift, and porting them in the opposite direction to make the Obj-C header files. If you’re going annotate things, it would be more effective to start from the more expressive language. Actually, I’m not at all sure there isn’t a place for user-written “header” files in Swift generally. It’s duplicative, I know, but it’s much better documentation (especially of public APIs) than the actual source files. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
