<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">-1 for specifying errors for throws. Please don't. Proven by practice in java it's a nightmare.</span></div></blockquote></div><div class="">In Java, this topic is really interesting:</div><div class="">It sounds like a great idea, but in real-life situations, afaics everyone hates checked exceptions.</div><div class=""><br class=""></div><div class="">But Swift isn't Java, and our error handling is different from most established languages, so imho we shouldn't base that decision on experiences from other models only:</div><div class="">I don't see downsides, because you already need "try" for everything that can throw, and afaics, it would be easy to ignore the information that only a set of exceptions can happen in a given context.</div><div class=""><br class=""></div><div class="">So, imho before there is a decision wether "throws" should be moved, the possibility to annotate it with a fixed set of error types should be either abandoned or incorporated. </div></body></html>