Could such construct also allow for an if-else expression like behavior?<div><br></div><div>let result = if bool { 1 } else { 2 }</div><div><br></div><div><div><div> Or would this be better modeled as a non block-like expression? <br></div><div><br></div>let result = 1 if bool else 2</div><div><br></div><div>I'm just curious, this maybe be out of topic/ unrelated. <span></span><br><div><br><br>On Wednesday, December 9, 2015, Joe Groff via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><blockquote type="cite"><div>On Dec 9, 2015, at 8:47 AM, David Owens II <<a href="javascript:_e(%7B%7D,'cvml','david@owensd.io');" target="_blank">david@owensd.io</a>> wrote:</div><br><div><div style="word-wrap:break-word">Another language construct seems a bit much for this, right? Maybe I’m missing something, but can’t we get the same behavior with an overload?</div></div></blockquote><div><br></div><div>A language construct that helps eliminate multiple other language constructs would potentially be a net win, though. If there were closures that supported nonlocal exits, then `do`, `for...in`, and possibly other constructs could become library functions, and other "block-like" library features like `autoreleasepool`, `withUnsafePointer` would work more naturally too.</div><div><br></div><div>-Joe</div><br><blockquote type="cite"><div><div style="word-wrap:break-word"><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><font face="Menlo">extension Array {</font></div><div><font face="Menlo"> func forEach<U>(body: (element: Element) throws -> U?) rethrows -> U? {</font></div><div><font face="Menlo"> for e in self {</font></div><div><font face="Menlo"> if let result = try body(element: e) { return result }</font></div><div><font face="Menlo"> }</font></div><div><font face="Menlo"> </font></div><div><font face="Menlo"> return nil</font></div><div><font face="Menlo"> }</font></div><div><font face="Menlo">}</font></div><div><font face="Menlo"><br></font></div><div><font face="Menlo">func g(e: Int) -> Int? {</font></div><div><font face="Menlo"> if e == 2 { return e }</font></div><div><font face="Menlo"> return nil</font></div><div><font face="Menlo">}</font></div><div><font face="Menlo"><br></font></div><div><font face="Menlo">let arr = [1, 2, 3]</font></div><div><font face="Menlo">arr.forEach { print($0) }</font></div><div><font face="Menlo">let result = arr.forEach(g)</font></div><div><font face="Menlo">result // has the value of 2</font></div></blockquote><div><br></div><div><br></div><div>Now, Swift has some issues determining the types properly if you attempt to inline the g function at the forEach() callsite, but that can be fixed.</div><div><br></div><div>-David</div><div><br><div><blockquote type="cite"><div>On Dec 9, 2015, at 4:40 AM, Stephen Celis via swift-evolution <<a href="javascript:_e(%7B%7D,'cvml','swift-evolution@swift.org');" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br><div><div><blockquote type="cite">On Dec 8, 2015, at 5:13 PM, Joe Groff via swift-evolution <<a href="javascript:_e(%7B%7D,'cvml','swift-evolution@swift.org');" target="_blank">swift-evolution@swift.org</a>> wrote:<br><br>Another direction you might take this is to make it a type annotation on the function type, like throws, so forEach has a type like this:<br><br>func forEach(body: (Element) breaks -> ())<br><br>and a closure that `breaks` has nonlocal behavior for break/continue/return (and is implied to be noescape and void-returning, I guess).<br></blockquote><br>This is really interesting. Ruby provides similar functionality with its lambda vs. proc, but a type annotation is much more understandable. It could also imply @noescape automatically:<br><br> func forEach(@canbreak body: Element -> Void)<br><br>Stephen<br>_______________________________________________<br>swift-evolution mailing list<br><a href="javascript:_e(%7B%7D,'cvml','swift-evolution@swift.org');" target="_blank">swift-evolution@swift.org</a><br><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br></div></div></blockquote></div><br></div></div></div></blockquote></div><br>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=OWK4tSasaK2n-2FQIIcS9Ug-2FuFXG-2BJ3z6cFMLgm306hDeZJdKs1ugeNhhMygXsrPAgjehoXRT16GBxVOGmyGDsup-2Fn3MHhLl0XMH864JXI1nR250mX-2BPszWE07Yy31et1U-2F796OmdPrK7ao-2B5AgGbrtRFd2cGCSlhLfLw16nuQzpTlzRCWKbM8KQpgoSb-2Bj5ABYT62n93ZuSf1j0P3m0f63FMD3c2MXvAnKLbn5Fu4xec-3D" alt="" width="1" height="1" border="0" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important">
</div>
</blockquote></div></div></div>