As I wrote above, where you are assigning a type at that moment - no. Its quite obvious. You're doing it right there where its obvious. Frankly, I don't see the two things as being the two sides of the same coin. In one case the type is seen pretty obviously because you're assigning it. In the other you're passing arguments and its not obvious in most cases.
On Wed, Jun 24, 2015 at 4:35 PM, Rick Mann <rm...@latencyzero.com> wrote: > > > On Jun 24, 2015, at 15:25 , Alex Kac <a...@webis.net> wrote: > > > > I guess I cannot agree with you, Rick. I love the fact that Objective-C > and now Swift require parameter names. I prefer verbose function names, > parameters, etc.. than obtuse ones. I don't want to have to infer. I want > it to be explicit. Infering types works because let myAttribString = > NSMutableAttributableString() is very clear. That's my two cents. > > Again, I'm just asking for the option. I'm not saying it should be removed > from the language. > > Let me ask you this: do you also feel like you should specify variable > types? > > > -- > Rick Mann > rm...@latencyzero.com > > > -- *Alex Kac - **President and Founder* *Web Information Solutions, Inc.* _______________________________________________ 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
