<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Nov 9, 2017, at 4:01 PM, Paul Cantrell <<a href="mailto:paul@bustoutsolutions.com" class="">paul@bustoutsolutions.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class=""><span class="Apple-converted-space"> </span>using the same name for both flatMap variants causes the type checker to miss programmer errors</span></div></blockquote></div><br class=""><div class="">Not to mention, makes it do a lot more work, lengthening compile times (especially when mixed with closure and literal type inference… the combinations, they explode).</div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>