[swift-evolution] Idea: change "@noreturn func f()" to "func f() noreturn"
Radosław Pietruszewski
radexpl at gmail.com
Thu Feb 25 16:38:47 CST 2016
The difference though is that throws/rethrows is a part of type signature, @noreturn isn’t and has no reason to be AFAICT. It’s just an attribute of the method…
— Radek
> On 25 Feb 2016, at 22:44, Jacob Bandes-Storch via swift-evolution <swift-evolution at swift.org> wrote:
>
> Premise: there are multiple ways of describing control-/data-flow when a function is called:
>
> func x() -> T // x returns a value, of type T, to the caller
> func x() throws // x may throw an error to the caller
> func x() throws -> T // x may throw an error, and also return a value
> func x(...) rethrows ... // if a closure argument can throw an error, x may also throw
> @noreturn func x() // x never returns to the caller
>
> "noreturn" is currently spelled as an attribute, but like "throws" / "rethrows" / "-> T", it's really describing how control flow works.
>
> IMO this calls for consistency: whatever happens "after" the function is called should appear "after" the parameter list.
>
> func x() noreturn {
> ...
> }
>
>
> Thoughts?
>
> Jacob
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160225/ef1ae198/attachment-0001.html>
More information about the swift-evolution
mailing list