<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I too am happy with the status quo.<div class=""><br class=""></div><div class="">As a reminder, structured markup supports "- throws:" annotation</div><div class=""><br class=""></div><div class="">-- E</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 4, 2017, at 5:10 AM, Jeremy Pereira via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><blockquote type="cite" style="font-family: Palatino-Roman; font-size: 14px; 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-size-adjust: auto; -webkit-text-stroke-width: 0px;" class=""><br class="Apple-interchange-newline">On 3 Jan 2017, at 16:29, John McCall via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><br class=""><br class=""><br class="">I'm sorry if people dislike the placement of "throws", but that ship has sailed,<br class="">and any attempt to "fix" it at this point is just going to cause problems for<br class="">negligible benefit.<br class=""><br class="">As I see it, the current syntax has one mild deficiency, called out previously<br class="">in this thread: a reader has to recognize that "throws -> X" does not mean<br class="">that the function throws an X, but instead that it either throws or returns an X.<br class="">It's always nice when something is immediately obvious and doesn't have to<br class="">be explicitly learned, and I appreciate and mourn that my design may have<br class="">fallen short of that standard here. However, overall I still do think the syntax<br class="">is much cleaner than the alternatives, especially as return types grow more<br class="">complicated, and that this small rule is not at all difficult to master.<br class=""></blockquote><br style="font-family: Palatino-Roman; font-size: 14px; 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;" class=""><span style="font-family: Palatino-Roman; font-size: 14px; 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="">I’m going to stand up for the way it is now. I do not think the design falls short or is deficient. </span></div></blockquote><br class=""></div></div></body></html>