> On Oct 19, 2014, at 00:54 , Quincey Morris > <quinceymor...@rivergatesoftware.com> wrote: > > If, hypothetically, a subclass was allowed to call any initializer in the > superclass, then the result would be an object that was fully (“correctly”) > initialized in terms of the superclass, but that doesn’t mean it’s fully > initialized in terms of the subclass.
The subclass initializer still has to initialize itself. It knows what the superclass initializer is doing, and it knows what it still needs to do. That's true even with the rules Swift currently imposes. > In Swift, an external caller cannot initialize a class by calling one of its > superclass initializers — formally. In practice, there are two cases: Of course, not, and I'm not suggesting that at all. -- Rick Mann rm...@latencyzero.com _______________________________________________ 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
