I tried hard find all references to 'func' in documentation, comments and
diagnostics, but I am sure that I missed a few. If you find something, please
let me know.
rdar://15346654
Swift SVN r9886
This was not likely an error-free change. Where you see problems
please correct them. This went through a fairly tedious audit
before committing, but comments might have been changed incorrectly,
not changed at all, etc.
Swift SVN r7631
Currently only used for parsing. The immediate intent of these attributes is
to have them behave like [objc] for the purpose of emitting method
implementations; however, they are semantically distinct and should only be
used to expose outlets and actions to Interface Builder.
Swift SVN r3416
IBOutlet and IBAction are used by Xcode to support XIB editing, but moreover
there is not an /inherent/ requirement that they imply [objc]. For [IBAction],
it seems unlikely that this will ever change, but [IBOutlet] already tries
several different ways to make its connection, and moreover with outlets for
which we can see the declaration, *the type of the object is known,*, and IB
could in theory know to use the Swift entry points.
IBOutlet and IBAction are currently recognized; my plan is to make them both
alias [objc] internally for now.
Swift SVN r3317
Most notably, every Swift object will be id-compatible and have an isa.
Swift classes that do not inherit from an Objective-C class will be marked
unavailable in an Objective-C source file, but their instances can be
referred to by protocol ('id <NSApplicationDelegate>') or by plain 'id'.
I've updated some of the "Use Cases" with some "guidelines" that would
eventually make their way into, say, DevPubs articles (a long way down
the line).
Swift SVN r3092
The new section is supposed to discuss the different models for various
pieces of infrastructure (messaging, methods, classes, subclassing, and
overriding) -- basically, how much of Swift is exposed to Objective-C.
I think the big issue right now is actually what I've labeled the
Messaging Model: whether arbitrary Swift-objects are id-compatible. That
basically has repercussions everywhere else.
This doc is kind of a mess right now, I know.
Swift SVN r3072
