<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Jan 26, 2016 at 1:57 PM, Dave Abrahams via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:</div><div class="gmail_quote"><br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"> $ git grep -nHE -e 'func [a-z]*ing\>\(\)' | grep -v 'string()'<br> ../../Platforms/OSX/DiscRecording.swift:678: func encoding() -> UInt<br> ../../Platforms/OSX/Quartz.swift:1822: func mirroring() -> Bool<br> ../../Platforms/OSX/SceneKit.swift:4762: class func spring() -> SCNPhysicsField<br> ../../Platforms/OSX/WebKit.swift:340: func padding() -> String!<br> ../../Platforms/iOS/SceneKit.swift:4474: class func spring() -> SCNPhysicsField<br> ../../Platforms/iOS/UIKit.swift:2237: func reversing() -> UIBezierPath<br> ../../Platforms/tvOS/SceneKit.swift:4474: class func spring() -> SCNPhysicsField<br> ../../Platforms/tvOS/UIKit.swift:1723: func reversing() -> UIBezierPath<br> ../../Platforms/watchOS/UIKit.swift:424: func reversing() -> UIBezierPath<br>Except for reversing, these are all fine AFAICT.</blockquote><div><br></div></div><div class="gmail_quote">Here are some others from the swift-3 branch; I'm not sure where these currently fall under the guidelines:</div><div class="gmail_quote"><br></div><div class="gmail_quote">CIImage</div><div class="gmail_quote"><div class="gmail_quote"> func byCompositingOverImage(dest: CIImage) -> CIImage</div><div class="gmail_quote"> func byCroppingTo(rect: CGRect) -> CIImage</div><div class="gmail_quote"> func byClampingToExtent() -> CIImage</div><div class="gmail_quote"><br></div><div class="gmail_quote">(NS)IndexPath</div><div class="gmail_quote"> func removingLastIndex() -> IndexPath<br></div><div class="gmail_quote"><br></div><div class="gmail_quote">SKTexture</div><div class="gmail_quote"> func generatingNormalMap() -> Self</div><div class="gmail_quote"> func generatingNormalMapWithSmoothness(smoothness: CGFloat, contrast: CGFloat) -> Self</div></div><div class="gmail_quote"><br></div><div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">> class func *darkGray*() -> UIColor<br>
><br>
> I would rather see this imported as `class var *DarkGray*: UIColor { get }`.<br>
<br>
Why should we capitalize some vars and not others?<br></blockquote><div><br></div><div>I was hoping that colors, and other such types with class methods returning particular instances, would be treated like enum cases.</div><div><br></div><div>enum UIColor {</div><div> case DarkGray</div><div> case Black</div><div> case Clear</div><div> ...</div><div>}</div><div><br></div><div>enum CAMediaTimingFunction { // more of a job for an overlay, since these are created with init(name: String)</div><div> case Linear</div><div> case EaseInEaseOut</div><div> ...</div><div>}</div><div><br></div><div>In the meantime, of course, I saw there was some discussion of having enum cases begin with lowercase letters as well. I could get used to that. (I'd just like these to be consistent.)</div></div></div></div>