<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="">Also this is not without precedent and feels more swift like to me. In switch cases you can include or drop the let or the var. <div class=""><br class=""></div><div class="">for example;</div><div class=""><br class=""></div><div class="">switch coord {</div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">case (let x, _): print(x)</div><div class="">case (_, let y); print(y)</div><div class="">case let (x, y): print(x,y)</div></blockquote><div class="">}</div><div class=""><br class=""></div><div class="">underscore does not need the keyword let here.</div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 24, 2016, at 9:59 PM, Paul Ossenbruggen <<a href="mailto:possen@gmail.com" class="">possen@gmail.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="">Since we don’t care about the result?<div class=""><br class=""></div><div class="">_ = ignoreResult()</div><div class=""><br class=""></div><div class="">It does not matter whether it is mutable or not so dropping the keyword is ok here. This is really obvious what it does and is concise. </div><div class=""> </div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Feb 24, 2016, at 9:54 PM, Charles Kissinger <<a href="mailto:crk@akkyra.com" class="">crk@akkyra.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=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Feb 24, 2016, at 9:19 PM, Paul Ossenbruggen <<a href="mailto:possen@gmail.com" class="">possen@gmail.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="">These lack conciseness. What about the already supported: <div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div style="font-size: 13px;" class=""><b class="">let _ = </b>ingoreResult()</div></blockquote></div></div></blockquote><div class=""><br class=""></div><div class="">I would be perfectly happy with requiring “let _ = “ myself. My recollection of the previous discussion is that most people didn’t want that to be necessary and preferred a suppressible warning.</div><div class=""><br class=""></div><div class="">Thinking about the attribute name some more, I might prefer:</div><div class=""><br class=""></div><div class="">@NoUnusedResultWarning</div><div class=""><br class=""></div><div class="">which is a variation of one of Erica’s suggestions. It is at least slightly shorter than @SuppressUnusedResultWarning</div><div class=""><br class=""></div><div class="">—CK</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div><div class="">Where ignoreResult is the function. Or maybe something even more brief? What was wrong with (void)? or </div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>(_)ingoreResult()</div><div class=""><br class=""></div><div class="">- Paul </div><div class=""><br class=""></div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Feb 24, 2016, at 8:42 PM, Charles Kissinger 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=""><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=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Feb 24, 2016, at 7:12 PM, Erica Sadun 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=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">I'd rather have something clear than short.</div><div class=""><br class=""></div><div class="">Some short ones that haven't been mentioned:</div><div class=""><ul class=""><li class="">@Statement has a problem because the result can be used, it's just not mandated. </li><li class="">@Statementable just makes no English sense at all (similarly @Procedurable) but kind of communicates the idea</li><li class="">@ResultDiscardable: not a fan</li><li class="">@StatementAllowed or @AllowStatement really doesn't make a ton of sense, but it's short and kind of gets the point across.</li><li class="">@SideEffects also short, also kind hints at stuff, also could be misleading, and the same for @HasSideEffects.</li></ul></div><div class="">My favorite remains <font face="Menlo" class="">@SuppressUnusedResultWarning</font><span style="font-family: Palatino-Roman;" class="">, which isn't short but pretty damn clear.</span></div></div></div></blockquote><div class=""><br class=""></div><div class="">+1. This would be my choice as well. It is the warning that is affected, not the result, so “Warning” or “NoWarn” should be in the name.</div><div class=""><br class=""></div><div class="">—CK</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""> </div><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Feb 24, 2016, at 7:32 PM, Brent Royal-Gordon 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=""><div class=""><blockquote type="cite" class="">@optional_result (or ideally @optionalResult if camel-case for attributes is accepted) is clearer I think if we want a shortened two-word form.<br class=""></blockquote><br class=""></div></div></blockquote></div><br class=""></div>_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div></blockquote></div><br class=""></div>_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></body></html>