<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<div name="messageBodySection" style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;">
<div>I don't think anybody wants a big discussion out of this, but if there's a chance that the name will be further revised, then I agree with Nevin, the solo "compacted" is a more appropriate term than "compacting" here. Compacting needs an grammatical object to apply to, so if we wanted to use that form, "compactingElements" would be the proper way to phrase it.</div>
<div><br /></div>
<div>"compactingMap" works, because the map operation is being compacted. But "compactedMap" also works, because it's a compacted form of the map operation.</div>
<div><br /></div>
<div>So if we want to revise the naming, I would suggest "compacted" and "compactedMap". But I think the accepted naming is fine as well, and we should avoid "compacting".</div>
</div>
<div name="messageSignatureSection" style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;"><br />
Jarod</div>
<div name="messageReplySection" style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;"><br />
On Dec 19, 2017, 15:52 -0800, Nevin Brackett-Rozinsky via swift-evolution <swift-evolution@swift.org>, wrote:<br />
<blockquote type="cite" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #1abc9c;">
<div dir="ltr">If we’re bikeshedding the verb tense then “compactMap” sounds right to me, and adding “ing” would be needlessly verbose.
<div><br /></div>
<div>For the non-mapping version, I’d lean toward “compacted”. However, we could also postpone the debate over its spelling until such time as we are actually ready to introduce it.</div>
<div><br /></div>
<div>Nevin</div>
<div><br /></div>
<div><br /></div>
</div>
<div class="gmail_extra"><br />
<div class="gmail_quote">On Tue, Dec 19, 2017 at 6:42 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: 5px 5px; padding-left: 10px; border-left: thin solid #e67e22;">
<div style="word-wrap:break-word;line-break:after-white-space"><span class=""><br /></span>
<div><span class=""><br /></span>
<blockquote type="cite" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #3498db;"><span class=""></span>
<div><span class="">On Dec 19, 2017, at 2:28 PM, Xiaodi Wu via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</span></div>
<span class=""><br class="m_-1493299564316744864Apple-interchange-newline" /></span>
<div><span class="">I disagree. Let’s not reopen what is settled. “Compact” can be a noun just as “map” and “filter” can; as long as there are no in-place variants, there can be no ambiguity.<br /></span>
<div class="gmail_quote"><span class=""></span>
<div dir="ltr"><span class="">On Tue, Dec 19, 2017 at 17:11 Brent Royal-Gordon via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br /></span></div>
<blockquote class="gmail_quote" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #d35400;"><span class=""></span>
<div style="word-wrap:break-word;line-break:after-white-space"><span class=""></span>
<div><span class=""></span>
<blockquote type="cite" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #34495e;"><span class=""></span>
<div><span class="">On Dec 19, 2017, at 8:56 AM, John McCall <<a href="mailto:rjmccall@apple.com" target="_blank">rjmccall@apple.com</a>> wrote:</span></div>
<span class=""><br class="m_-1493299564316744864m_4244156192150185115Apple-interchange-newline" /></span>
<div><span class=""><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">Therefore, SE-0187 is<span class="m_-1493299564316744864m_4244156192150185115Apple-converted-space"> </span></span><b style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">accepted</b><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">, with the<span class="m_-1493299564316744864m_4244156192150185115Apple-converted-space"> </span></span><b style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">revision</b><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important"><span class="m_-1493299564316744864m_4244156192150185115Apple-converted-space"> </span>that the new name be Sequence.compactMap(_:), and with the agreement that we will add Sequence.compact() when it is possible to do so.</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" /></span></div>
</blockquote>
</div>
<div><br /></div>
</div>
<div style="word-wrap:break-word;line-break:after-white-space">
<div>I like `compact` as the basis for the name, but I hope the core team will consider whether the eventual nil-removal method should be called `compacting()`, and whether therefore this method should be called `compactingMap(_:)`. Prior art on the name `compact()` does exist, but I don't think it's strong enough to justify deviating from the API Guidelines.</div>
<div><br /></div>
<div>I don't think we need a full review on this tiny issue; five minutes of the core team's time should more than suffice.</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
<br />
<div>I agree with Brent. IMO we're firmly outside the domain of established terms-of-art here (Ruby notwithstanding). </div>
</div>
<br />
______________________________<wbr />_________________<br />
swift-evolution mailing list<br />
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br />
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr />mailman/listinfo/swift-<wbr />evolution</a><br />
<br /></blockquote>
</div>
<br /></div>
_______________________________________________<br />
swift-evolution mailing list<br />
swift-evolution@swift.org<br />
https://lists.swift.org/mailman/listinfo/swift-evolution<br /></blockquote>
</div>
</body>
</html>