<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 24 Feb 2016, at 23:44, Janosch Hildebrand <<a href="mailto:jnosh@jnosh.com" class="">jnosh@jnosh.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Thanks for the encouragement everyone! I’ll start drafting over the weekend.</div><div class=""><br class=""></div><div class="">With regard to the inverted attribute, that is definitely open to discussion.</div><div class="">Other variants that had been mentioned previously include:</div><div class=""><br class=""></div><div class="">@suppress_unused_result - suggested by Adrian Kashivskyy</div><div class="">@allow_unused_result - suggested by Kevin Ballard</div><div class="">@ignoreresult - suggested by Brent Royal-Gordon</div><div class=""><br class=""></div><div class="">Also the aforementioned “Modernizing Attribute Case and Attribute Argument Naming” proposal[1] will also play into this discussion as well.</div><div class=""><br class=""></div><div class="">[1] <a href="https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160215/010510.html" class="">https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160215/010510.html</a></div><div class=""><br class=""></div><div class="">- Janosch</div></div></div></blockquote><br class=""></div><div>While I like the brevity, I don’t think @ignoreresult is clear enough on what it does, @optional_result (or ideally @optionalResult if camel-case for attributes is accepted) is clearer I think if we want a shortened two-word form. Or there’s Sean’s @discardable_result alternative which is even clearer.</div><div><br class=""></div><div>Otherwise @allow_unused_result is the best of the three word options I think; @suppress_unused_result is a bit unclear as what you’re actually suppressing is the compiler warning, as in most cases a result will still be generated, it’s just not stored anywhere at the call site.</div></body></html>