[swift-evolution] SE-0047

https://github.com/apple/swift-evolution/blob/master/proposals/0047-nonvoid-warn.md I really like the way Swift currently works in this regard. Return values can be and are routinely ignored and that is ok an

Re: [swift-evolution] SE-0047

> It is far more common to be able to ignore a return value than to have it be > required to be handled. Do you really think that's true? I took a look at the Swift standard library and extracted just the function, method, and operator names and return values, with Void functions excluded (sin

Re: [swift-evolution] SE-0047

I don't think that counting discardable results in existing Cocoas libraries is a good metric for the usefulness of warn-unused-result: Other libraries may follow a different style, and Objective-C is a very bad fit for fluent interfaces. So far, I haven't seen any real world examples of problem