<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">Are you encouraging the use of non-local returns to work around a limitation of the language?</div><div class=""><br class=""></div><div class="">Literally all new programming languages made these days have such a short-circuiting construct some way or another that doesn't translate to non-local returns. I don't see what makes Erlang so special that you would argue it doesn't need one.<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Le 7 déc. 2018 à 12:28, Kenneth Lundin <<a href="mailto:kenneth@erlang.org" class="">kenneth@erlang.org</a>> a écrit :</div><br class="Apple-interchange-newline"><div class=""><p style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">It is perfectly possible to use throw and try catch to replace or simplify deeply-nested case ... end expressions in the same way as the proposed language extension does</p><a name="m_-8746844382255813045_m_7746986015464219343_Example" id="gmail-m_-8746844382255813045gmail-m_7746986015464219343gmail-Example" style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""></a></div></blockquote></div></div></body></html>