<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On Oct 30, 2016, at 5:49 AM, Jody Schofield via swift-dev <<a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a>> wrote:</div><div class=""><div dir="ltr" class=""><div style="font-size:13px" class="">Sorry, I'm sure this has been discussed before, but what the heck???</div><div style="font-size:13px" class=""><br class=""></div><div style="font-size:13px" class="">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" class=""><br class=""></div><div style="font-size:13px" class="">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></div></blockquote><div><br class=""></div></div><div class="">I think we're generally very comfortable with this rule; forgetting to handle a return value (maybe because you expect the function to be mutating) is a pretty common mistake, and "_ = " seems nicer than the old C equivalent "(void)".</div><div class=""><br class=""></div>Do you find yourself writing a lot of functions that return non-void results that you frequently want to ignore? Maybe there's some idiom we could do a better job of recognizing.<div class=""><br class=""></div><div class="">John.</div></body></html>