<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 2 Mar 2016, at 12:20, Tino Heth via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">discardable return values are no anti-pattern, so I don't think they should be punished with a monstrosity like "@dont_warn_unused_result" (shiver).</div></blockquote><br class=""></div><div>Firstly; you seem to have picked the worst possible attribute name. People seem to be favouring a @discardable attribute on the return type itself, so something like:</div><div><br class=""></div><div><font face="Monaco" class=""><span class="Apple-tab-span" style="white-space:pre"> </span>func myFunction() -> @discardable String { … }</font></div><div><br class=""></div><div>The question really is whether you think functions with intentionally discardable results are in the minority or not. In my experience they’re pretty uncommon, and designed to be usable in that way, in which case it makes sense for an explicit declaration to clarify that intent, both to the compiler to ensure that it isn’t seen a potential mistake, but also to developers in documentation, where a return value can be clearly marked as discardable.</div></body></html>