I'm not going to go as far as a definitive +1, but I've definitely wanted this
for var and subscript getters. If it were limited to single-expression
functions, I don't see much harm. The only time there'd be a problem is if the
return types matched and you were going to have another statement instead.
It feels weird for anything imperative, but I think the whole point is that
there are plenty of functions which do absolutely no imperative work. I
personally wouldn't want people to start using it for forwarding imperative
things, though.
func sendHTTPRequest() -> Result {
sendHTTPRequestImpl(destinationURL, body)
}
Jordan
> On Dec 19, 2015, at 5:30 , Craig Cruden via swift-evolution
> <[email protected]> wrote:
>
>
> When writing short functional code in a function it would be nice if the
> return keyword were an optional keyword.
>
> Just return the last evaluated expression.
>
>
> i.e.
>
> func flipFunc<T, U>(arg1: T, arg2: U) -> (U, T) {
> (arg2, arg1)
> }
>
>
> The keyword return would still be there for breaking out of a function.
>
> _______________________________________________
> swift-evolution mailing list
> [email protected]
> https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
