+1 for removing Error protocol. Then it's a breaking change, and this edition of the proposal can be reviewed for Stage 1. Swift error model tries to be different (better) than of other languages. We encourage not to rethrow, but to think of errors as of meaningful results and process them accordingly, at all levels of abstraction. Right now, the formal proposal can't be submitted, but discussion is fine.
2016-08-29 12:18 GMT+03:00 Tino Heth via swift-evolution < swift-evolution@swift.org>: > I'm quite skeptical here (Java has already been mentioned…), but if it's > done, I'd vote for removing ErrorType: > This empty protocol always felt a little bit odd to me, and when each > function has information about what errors to expect, imho there is > absolutely no benefit associated with conformance. > Even now, it's not that much — or does anyone actually consult a list of > conforming types for error handling?
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
