On Mar 11, 2015, at 14:49 , Marco S Hyman <m...@snafu.org> wrote: > Perhaps you are thinking of them that way because of your C/Obj-C background. >
I was thinking of them that way because I didn’t have a better term. :) > Think of them instead as abbreviated .swift files. Very good. So, in the fantasy world of this hijacked thread [apologies to the OP], I want two things: 1. The ability to create my own abbreviated Swift files, technically duplicative, but convenient as a means of compactly documenting an API in my own classes. 2. The SDKs to be written in abbreviated Swift files, instead of Obj-C header files, wherever interoperable, since Swift is already more expressive. (And then these abbreviated Swift files to be updated for the purpose Charles proposed, instead of inventing annotations for Obj-C.) I dunno, but it seems to me that we’re not so very far away from being able to do both these things. _______________________________________________ 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
