> On Jun 29, 2015, at 3:42 PM, Rick Mann <rm...@latencyzero.com> wrote: > > Here's an example (and this is what I frequently encounter) where requiring > parameter names adds nothing but clutter: > > let config = WKWebViewConfiguration() > self.webView = WKWebView(frame: self.webViewContainer.frame, > configuration: config); > > Moreover, when you're skimming the code, it looks a bit like the WKWebView > constructor takes four arguments, not two. If you work the way I do, which is > to skim pages of code for shapes (e.g., I know the constructor takes two > parameters, so I can quickly zero in on a thing that looks like a call with a > couple of parameters, delimited by white space, and then look more closely to > see if it's the one I wanted. The extra islands of text from parameter names > throws that off).
Perhaps you would prefer a different whitespace convention, one with no spaces around the colon in actual parameters. That's a popular convention in Objective-C. Otherwise there is no difference between Objective-C and Swift here. -- Greg Parker gpar...@apple.com Runtime Wrangler _______________________________________________ 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
