[swift-evolution] Disallowing unreachable code

David Sweeris davesweeris at mac.com
Mon Mar 27 14:54:57 CDT 2017

> On Mar 27, 2017, at 11:27 AM, Peter Dillinger via swift-evolution <swift-evolution at swift.org> wrote:
>> -1, for all the reasons others have already explained. This unnecessarily complicates the debugging process. If you ship code with warnings still in it, that’s your own fault.
> All the obsolete/unfounded reasons?  Please address my technical arguments directly, rather than in the (potentially stale/unfounded) abstract.

-1, because having to write out “if(true) {…}” just because somebody might ignore a warning is annoying.

I wouldn’t object to the “—treatWarningsAsErrors” flag someone else mentioned.

- Dave Sweeris

More information about the swift-evolution mailing list