> On Nov 25, 2015, at 01:04 , Quincey Morris > <quinceymor...@rivergatesoftware.com> wrote: > > In a technical sense, the reason is probably that Swift allows class/static > and instance members to have the same name, presumably because it has to > support Obj-C methods, where the same thing can happen. That means there’s a > danger of ambiguity, and it was probably decided that the clunkier > disambiguation would lead to fewer programmer errors.
Still seems like Swift could use some scope resolution, and just complain if it's ambiguous. Anyway, thanks. I'll write it up as a feature request. -- 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
