On Aug 10, 2014, at 06:46 , Roland King <r...@rols.org> wrote: > And if anyone thinks Swift is all simplicity and scripty loveliness I came > across this StackOverflow question and answer today. It will be a while > before I entirely understand it, it will be a long while before I could > attempt to reproduce it.
Deliberately missing your point, I’d say the problem is that Swift has two kinds of generics — one for class types and one for protocols. The concepts are fairly easy to grasp individually, but become horrendously complex when allowed to interact. Personally, I regard this as a bug in the language design. OTOH, C++ has historically proved that generics (i.e. templates) *alone* can become horrendously complex. Even on this list, the most common C++ question is, “Why won’t my template instantiate properly?”. One of the joys of Obj-C has always been that it isn’t very ambitious in the language-features department. Remember the fuss when property syntax was introduced? _______________________________________________ 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
