[swift-evolution] Guard Implicit Fallback

Developer devteam.codafi at gmail.com
Thu Feb 11 11:38:50 CST 2016

I agree the nil fallback case is a common one, but the loss of readability and decreased understanding of control flow here makes me think special-casing this isn't all it's cracked up to be.

~Robert Widmann

2016/02/10 22:40、Tighe Racicot via swift-evolution <swift-evolution at swift.org> のメッセージ:

> Hey everyone, 
> I feel that `guard` could be a little more Swifty and would like to start a conversation concerning it.
> For example, I often have a function whose job depends on an optional having a value, and so I guard-let at the start and return if the guard fails. Or if the function returns an optional type, I'll simply return nil if guard fails. 
> Can we improve on the general fallback case? Could we simply say:
> func noReturn() {
>     guard let aValue = someOptional
>     ....
> }
> and have that imply "else { return void or nil }"
> What are your thoughts?
> Tighe
> _______________________________________________
> 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/20160211/1920add6/attachment.html>

More information about the swift-evolution mailing list