On Mar 10, 2015, at 22:57 , dangerwillrobinsondan...@gmail.com wrote: > > This is one extra thing you have to really get used to with Swift. You learn > Swift, then learn that it effectively requires some constant special handling > for NSObject's descendants. > If you're using the frameworks that's a lot of optionals and implicitly > unwrapped optionals.
It’s not the optionals that are the problem, nor the implicit unwrapping. Those things are just the symptoms in this case. The problem I was referring to was implicit forced downcasting. It seems so arbitrary — both the fact that it downcasts without provocation, and the (apparent, potential) randomness of what it downcasts to. _______________________________________________ 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
