[swift-evolution] Move placement of 'throws' statement

Erica Sadun erica at ericasadun.com
Wed Jan 4 14:43:04 CST 2017

I too am happy with the status quo.

As a reminder,  structured markup supports "- throws:" annotation

-- E

> On Jan 4, 2017, at 5:10 AM, Jeremy Pereira via swift-evolution <swift-evolution at swift.org> wrote:
>> On 3 Jan 2017, at 16:29, John McCall via swift-evolution <swift-evolution at swift.org> wrote:
>> I'm sorry if people dislike the placement of "throws", but that ship has sailed,
>> and any attempt to "fix" it at this point is just going to cause problems for
>> negligible benefit.
>> As I see it, the current syntax has one mild deficiency, called out previously
>> in this thread: a reader has to recognize that "throws -> X" does not mean
>> that the function throws an X, but instead that it either throws or returns an X.
>> It's always nice when something is immediately obvious and doesn't have to
>> be explicitly learned, and I appreciate and mourn that my design may have
>> fallen short of that standard here. However, overall I still do think the syntax
>> is much cleaner than the alternatives, especially as return types grow more
>> complicated, and that this small rule is not at all difficult to master.
> I’m going to stand up for the way it is now. I do not think the design falls short or is deficient. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170104/50d7257e/attachment.html>

More information about the swift-evolution mailing list