<html><head><style>
body {
font-family: "Helvetica Neue", Helvetica, Arial, sans-serif;
padding:1em;
margin:auto;
background:#fefefe;
}
h1, h2, h3, h4, h5, h6 {
font-weight: bold;
}
h1 {
color: #000000;
font-size: 28pt;
}
h2 {
border-bottom: 1px solid #CCCCCC;
color: #000000;
font-size: 24px;
}
h3 {
font-size: 18px;
}
h4 {
font-size: 16px;
}
h5 {
font-size: 14px;
}
h6 {
color: #777777;
background-color: inherit;
font-size: 14px;
}
hr {
height: 0.2em;
border: 0;
color: #CCCCCC;
background-color: #CCCCCC;
display: inherit;
}
p, blockquote, ul, ol, dl, li, table, pre {
margin: 15px 0;
}
a, a:visited {
color: #4183C4;
background-color: inherit;
text-decoration: none;
}
#message {
border-radius: 6px;
border: 1px solid #ccc;
display:block;
width:100%;
height:60px;
margin:6px 0px;
}
button, #ws {
font-size: 12 pt;
padding: 4px 6px;
border-radius: 5px;
border: 1px solid #bbb;
background-color: #eee;
}
code, pre, #ws, #message {
font-family: Monaco;
font-size: 10pt;
border-radius: 3px;
background-color: #F8F8F8;
color: inherit;
}
code {
border: 1px solid #EAEAEA;
margin: 0 2px;
padding: 0 5px;
}
pre {
border: 1px solid #CCCCCC;
overflow: auto;
padding: 4px 8px;
}
pre > code {
border: 0;
margin: 0;
padding: 0;
}
#ws { background-color: #f8f8f8; }
.bloop_markdown table {
border-collapse: collapse;
font-family: Helvetica, arial, freesans, clean, sans-serif;
color: rgb(51, 51, 51);
font-size: 15px; line-height: 25px;
padding: 0; }
.bloop_markdown table tr {
border-top: 1px solid #cccccc;
background-color: white;
margin: 0;
padding: 0; }
.bloop_markdown table tr:nth-child(2n) {
background-color: #f8f8f8; }
.bloop_markdown table tr th {
font-weight: bold;
border: 1px solid #cccccc;
margin: 0;
padding: 6px 13px; }
.bloop_markdown table tr td {
border: 1px solid #cccccc;
margin: 0;
padding: 6px 13px; }
.bloop_markdown table tr th :first-child, table tr td :first-child {
margin-top: 0; }
.bloop_markdown table tr th :last-child, table tr td :last-child {
margin-bottom: 0; }
.bloop_markdown blockquote{
border-left: 4px solid #dddddd;
padding: 0 15px;
color: #777777; }
blockquote > :first-child {
margin-top: 0; }
blockquote > :last-child {
margin-bottom: 0; }
code, pre, #ws, #message {
word-break: normal;
word-wrap: normal;
}
hr {
display: inherit;
}
.bloop_markdown :first-child {
-webkit-margin-before: 0;
}
code, pre, #ws, #message {
font-family: Menlo, Consolas, Liberation Mono, Courier, monospace;
}
.send { color:#77bb77; }
.server { color:#7799bb; }
.error { color:#AA0000; }</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class="bloop_markdown"><p>I’m still not convinced in some cases.</p>
<p>Take a look at <code>UIView</code>s and its method <code>addSubview</code>.</p>
<pre><code class="swift">open func addSubview(_ view: UIView)
</code></pre>
<p>Personally I’d change or write this function like so:</p>
<pre><code class="swift">open func add(subview: UIView)
</code></pre>
<p>This reduces unnecessary noise <code>_ view</code> for both the implementation and usage.</p>
<pre><code class="swift">// Implementation
open func add(subview: UIView) {
// `subview` is descriptive and just fine here
}
// Usage
self.view.add(subview: someOtherView)
</code></pre>
<p></p></div><div class="bloop_original_html"><style>body{font-family:Helvetica,Arial;font-size:13px}</style><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div> <br> <div id="bloop_sign_1476456293448583168" class="bloop_sign"><div style="font-family:helvetica,arial;font-size:13px">-- <br>Adrian Zubarev<br>Sent with Airmail</div></div> <br><p class="airmail_on">Am 14. Oktober 2016 um 16:42:06, Zach Waldowski via swift-evolution (<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>) schrieb:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>The base name of the function describes its core purpose.<br><br>There is no ambiguity instructing an Array to "append" something, but<br>there is context needed: "what are we appending? The contents of the<br>newElements parameter." But there is ambiguity asking URL to "give me a<br>new URL by appending". Appending what? Similarly, telling a collection<br>to "replace". Replace what?<br><br>A rule of thumb my team has applied is to put the parameter parens where<br>you would have put `with` in ObjC. This is instructive for your<br>questions as well. "URLByAppendingWithPathComponent" and<br>"replaceWithSubrange" wouldn't make sense, but "appendWithContentsOf"<br>does.<br><br>Cheers!<br> Zachary Waldowski<br> zach@waldowski.me<br><br>On Thu, Oct 13, 2016, at 10:30 PM, Charlie Monroe via swift-evolution<br>wrote:<br>> Hi there,<br>> <br>> I am really grateful for the API guidelines that were created as part of<br>> Swift 3, however, I'm having trouble with distinguishing which part of<br>> the method name should be already an argument. To illustrate this, here<br>> are two examples:<br>> <br>> // On Array<br>> public mutating func append(contentsOf newElements: S)<br>> <br>> // On Foundation.URL<br>> public func appendingPathComponent(_ pathComponent: String) -> URL<br>> <br>> <br>> Is there a particular reason why it's not<br>> <br>> public func appending(pathComponent: String) -> URL<br>> <br>> ?<br>> <br>> In my opinion the entire stdlib and Foundation is full of such<br>> discrepancies which make it hard to decide when you name your own methods<br>> since there are preceding cases in the language itself (or Foundation)<br>> that go both ways.<br>> <br>> The same goes for why don't the replace methods (this is on String)<br>> follow the same - when there is append(contentsOf:):<br>> <br>> public mutating func replaceSubrange(_ bounds: ClosedRange<String.Index>,<br>> with newElements: String)<br>> <br>> instead of<br>> <br>> public mutating func replace(subrange bounds: ClosedRange<String.Index>,<br>> with newElements: String)<br>> <br>> <br>> <br>> I know there was an extensive discussion about this here when the stdlib<br>> names were discussed. And given that these would be breaking changes, I<br>> don't necessarily want to start a lengthy discussion about renaming those<br>> again - I'm just wondering what are the reasons behind this and what<br>> should be the correct naming conventions.<br>> <br>> Thanks!<br>> <br>> Charlie<br>> _______________________________________________<br>> swift-evolution mailing list<br>> swift-evolution@swift.org<br>> https://lists.swift.org/mailman/listinfo/swift-evolution<br>_______________________________________________<br>swift-evolution mailing list<br>swift-evolution@swift.org<br>https://lists.swift.org/mailman/listinfo/swift-evolution<br></div></div></span></blockquote></div><div class="bloop_markdown"><p></p></div></body></html>