<div dir="ltr">+1 for removing Error protocol. Then it's a breaking change, and this edition of the proposal can be reviewed for Stage 1.<div><div>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.</div><div>Right now, the formal proposal can't be submitted, but discussion is fine.</div><div><div><div><div><div><div class="gmail_extra"><br><div class="gmail_quote">2016-08-29 12:18 GMT+03:00 Tino Heth via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm quite skeptical here (Java has already been mentioned…), but if it's done, I'd vote for removing ErrorType:<br>
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.<br>
Even now, it's not that much — or does anyone actually consult a list of conforming types for error handling?</blockquote></div></div></div></div></div></div></div></div></div>