[swift-evolution] proposal for a even simpler guard.. => guard!

Dominik Pich dominik at pich.info
Mon May 2 14:09:40 CDT 2016

often the guard statement is used to only unwrap optionals. multiple guards will cause a lot of ‘overhead’.
also often if it doesn’t work. there is no easy way we can gracefully recover ;)

so how about we do the same as with try/catch where you can use try! and have a guard!

the guard! could just throw an exception …

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

More information about the swift-evolution mailing list