<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Feb 17, 2016 at 3:49 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:<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"><span class=""><br>
on Wed Feb 17 2016, Jacob Bandes-Storch <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
<br>
> Question about how to interpret/apply the guidelines:<br>
><br>
> "[functions/methods] without side-effects should read as noun phrases…"<br>
> "Use the “ed/ing” rule to name the nonmutating counterpart of a<br>
> mutating method…"<br>
> "The names of other types, properties, variables, and constants should<br>
> read as nouns."<br>
><br>
> Within these guidelines, how do we explain why<br>
</span>> *-stringByExpandingTildeInPath* becomes "var *expandingTildeInPath*"? I'm<br>
<span class="">> wondering if the guidelines should clarify that the "ed/ing rule" may apply<br>
> to more than just nonmutating methods with mutating counterparts.<br>
<br>
</span>Why should it?<br></blockquote><div><br></div><div>Otherwise, it seems a case like this isn't really covered by the guidelines.</div><div> </div><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">
<span class=""><br>
> I think that "var expandingTildeInPath" is probably the best choice for<br>
> this API, but I can't figure out how to reconcile it with the guidelines as<br>
> written.<br>
<br>
</span>The guidelines don't force you to spell it that way, but they allow it.<br>
<br>
“x, expanding the tilde in its path”<br>
<br>
is a noun phrase.<br></blockquote><div><br></div><div>OK, I see. I guess what's confusing me is that I'm not sure why both the "ed/ing rule" and "read as noun" guidelines need to exist.</div><div><br></div><div>Maybe it would be clearer if the sentence were something like "The names of other types, properties, variables, and constants should read as nouns <b>at the point of use (possibly including the receiver in the noun phrase)</b>."</div><div><br></div></div></div></div>