<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=""><div><br class=""><blockquote type="cite" class=""><div 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; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Would this attribute not be a form of deprecation?</span></div></blockquote></div>So far, I only encountered deprecation in the context of legacy functionality that will be removed later — but after taking a look in the dictionary, I think the word is actually a good fit (even if there are no plans to remove flatMap).<div class=""><br class=""></div><div class=""><blockquote type="cite" class="">Yes, the rename has a fix-it, but still: to the extent that these things demand limited attention from the programmer, that attention should clearly be focused on the latter set of problems.</blockquote>I think there are worse warnings now:</div><div class="">Xcode suggests that a freshly declared var might be problematic, because you just did not have the time to write the code that changes it, that a let might be problematic because you can’t write the code to use that constant at the same time… I think this one here is rather helpful, as it educates you about a real (albeit small) error that can easily be avoided.</div><div class=""><br class=""></div><div class="">Even if filterMap is accepted, imho such a warning would be needed:</div><div class="">How should the same people that use flatMap wrong magically learn not to use filterMap all the time?</div></body></html>