<div><br><div class="gmail_quote"><div dir="auto">On Mon, Nov 13, 2017 at 10:02 AM C. Keith Ray via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br>
<br><div><blockquote type="cite"><div>On Nov 12, 2017, at 10:54 AM, Paul Cantrell via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br class="m_-5538535174283084733Apple-interchange-newline"><div><br><blockquote type="cite">On Nov 11, 2017, at 8:35 AM, Gwendal Roué via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br><br>I'd suggest `compactMap` as an alternative name, should `filterMap` find too much resistance:<br></blockquote><br>I like that name too, though it’s probably my Ruby experience showing. I like the clarity of “compact” for nils, “filter” for booleans. I like how fluently “compactMap” reads.<br><br>If the core team does accept this proposal, I’d trust them to take a minute to make a considered, opinionated choice about the name.<br><br></div></blockquote></div></div><div style="word-wrap:break-word"><div>You said "compact" removes nil values, so I'd name it "removeNils".</div></div></blockquote><div dir="auto"><br></div><div dir="auto"><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div></div></div>
</blockquote></div></div><div dir="auto">Terms like "ignoring" and "skipping".</div>