<html><body><div><br></div><div><br>Am 27. April 2016 um 01:16 schrieb Dave Abrahams <dabrahams@apple.com>:<br><br><div><blockquote type="cite"><div class="msg-quote"><div class="_stretch"><span class="body-text-content"><br>on Tue Apr 26 2016, Thorsten Seitz <tseitz42-AT-icloud.com> wrote:<br><br><blockquote type="cite" class="quoted-plain-text">Am 26. April 2016 um 01:16 schrieb Dave Abrahams via swift-evolution</blockquote><blockquote type="cite" class="quoted-plain-text"><swift-evolution@swift.org>:</blockquote><blockquote type="cite" class="quoted-plain-text"><br></blockquote><blockquote type="cite" class="quoted-plain-text">on Mon Apr 25 2016, Xiaodi Wu <xiaodi.wu-AT-gmail.com> wrote:</blockquote><blockquote type="cite" class="quoted-plain-text"><br></blockquote><blockquote type="cite" class="quoted-plain-text">Quick thought:</blockquote><blockquote type="cite" class="quoted-plain-text"><br></blockquote><blockquote type="cite" class="quoted-plain-text">Why are you reaching for the "form..." rule for the mutating methods when</blockquote><blockquote type="cite" class="quoted-plain-text">there</blockquote><blockquote type="cite" class="quoted-plain-text"><br></blockquote><blockquote type="cite" class="quoted-plain-text">are clear verb counterparts?</blockquote><blockquote type="cite" class="quoted-plain-text"><br></blockquote><blockquote type="cite" class="quoted-plain-text">location: locate</blockquote><blockquote type="cite" class="quoted-plain-text"><br></blockquote><blockquote type="cite" class="quoted-plain-text">successor: succeed</blockquote><blockquote type="cite" class="quoted-plain-text"><br></blockquote><blockquote type="cite" class="quoted-plain-text">We're not using successor(i) anymore, as noted below, and furthermore</blockquote><blockquote type="cite" class="quoted-plain-text">c.succeed(&i) strongly implies the wrong meaning. I didn't consider</blockquote><blockquote type="cite" class="quoted-plain-text">using</blockquote><blockquote type="cite" class="quoted-plain-text"><br></blockquote><blockquote type="cite" class="quoted-plain-text">c. locate(...:&i ... )</blockquote><blockquote type="cite" class="quoted-plain-text"><br></blockquote><blockquote type="cite" class="quoted-plain-text">primarily because I never thought of it and nobody suggested it IIRC,</blockquote><blockquote type="cite" class="quoted-plain-text">but I also don't see how it would work in a family with</blockquote><blockquote type="cite" class="quoted-plain-text">c.location(after: i) et al. Suggestions?</blockquote><blockquote type="cite" class="quoted-plain-text"><br></blockquote><blockquote type="cite" class="quoted-plain-text">What is wrong with</blockquote><blockquote type="cite" class="quoted-plain-text"><br></blockquote><blockquote type="cite" class="quoted-plain-text">c.locate(after: i)</blockquote><blockquote type="cite" class="quoted-plain-text"><br></blockquote><blockquote type="cite" class="quoted-plain-text">?</blockquote><br>Just to start with, it doesn't form a noun phrase.</span></div></div></blockquote></div><div><span><br data-mce-bogus="1"></span></div><div><span>Ah, my bad, I had completely missed the point of the problem (somehow thinking in the old model, not realizing that `c` is the collection and `i` to be mutated instead of `c`).</span></div><div><span><br data-mce-bogus="1"></span></div><div><span>Yeah, in that case I totally agree :-)</span></div><div><span><br data-mce-bogus="1"></span></div><div><span>Sorry for the noise...<br data-mce-bogus="1"></span></div><div><span><br data-mce-bogus="1"></span></div><div><span>-Thorsten</span></div><div><span></span><br></div></div></body></html>