<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Functions that return values return them for a reason. Ignoring them is, more likely than not, an oversight that should be corrected, hence @discardableResult. We're talking error codes, object lifetime tokens, failure indicators, etc. All things that result in ignoring critical code paths for the sake of convenience. If you find yourself executing a lot of side effects and ignoring return values, I would take a look at why. A lot of times you have control over the API and can eliminate some of these unused return values. Otherwise, please try to see if the return values of these functions are relevant to the well-being of your program.</div><div id="AppleMailSignature"><br>~Robert Widmann</div><div><br>2016/10/30 8:49、Jody Schofield via swift-dev <<a href="mailto:swift-dev@swift.org">swift-dev@swift.org</a>> のメッセージ:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div style="font-size:13px">Sorry, I'm sure this has been discussed before, but what the heck???</div><div style="font-size:13px"><br></div><div style="font-size:13px">This feature is killing me. Now I have go add @discardableResult to every function that returns a non-Void or use the ugly syntax `_ =`? </div><div style="font-size:13px"><br></div><div style="font-size:13px">Until swift 3 I've really enjoyed the new language. Now I find it to be getting too rigid for the sake of "protecting" me from myself. The safety levels needs to be dialled back some.</div><div style="font-size:13px"><br></div><div style="font-size:13px"><br></div></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-dev mailing list</span><br><span><a href="mailto:swift-dev@swift.org">swift-dev@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-dev">https://lists.swift.org/mailman/listinfo/swift-dev</a></span><br></div></blockquote></body></html>