<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <br>
    <br>
    <div class="moz-cite-prefix">On 3/14/2018 2:04 PM, Kevin Bourrillion
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAGKkBktGdTV_HqYx=eFH08caqkAaUNWR2de3m1ghkGg+ykudgw@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">On Wed, Mar 14, 2018 at 8:14 AM,
            Brian Goetz <span dir="ltr"><<a
                href="mailto:brian.goetz@oracle.com" target="_blank"
                moz-do-not-send="true">brian.goetz@oracle.com</a>></span>
            wrote:</div>
          <div class="gmail_quote"><br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF">In the meantime, let
                me probe for what's really uncomfortable about the
                current design point.  Is it:</div>
            </blockquote>
            <br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF">  - That we are
                overloading an existing control construct, "break", to
                mean something just different enough to be
                uncomfortable;<br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>To some degree yes, since `break <identifier>`
              already means something.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    We had rejected this earlier for fairly obvious reasons, but let me
    ask to get a subjective response: would using "return x" be better? 
    On the one hand, it's not really a return, and it doesn't build on
    the user intuition about the control flow aspects of break, but on
    the other, the return statement is already prepared to take a value,
    so its not adding a "new form" to the existing statement, though it
    is adding a new and different context.  (We abuse it slightly in
    lambdas, but people seem OK with this, probably because they think
    of lambdas as methods anyway.)  <br>
  </body>
</html>