> Agreed, we have the right design here. The go community has shown the result > of taking > a hard line on this, and it really hurts refactoring and other experimental > “pound out some > code” prototyping use cases. We use warnings for things that “should be > cleaned up before > code is committed”, but which is not itself a fatal issue.
Missing 'try' is a fatal issue? -- Peter Dillinger, Ph.D. Software Engineering Manager, Coverity Analysis, Software Integrity Group | Synopsys www.synopsys.com/software _______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
