<html><head><style>
body {
        font-family: "Helvetica Neue", Helvetica, Arial, sans-serif;
        padding:1em;
        margin:auto;
        background:#fefefe;
}
h1, h2, h3, h4, h5, h6 {
        font-weight: bold;
}
h1 {
        color: #000000;
        font-size: 28pt;
}
h2 {
        border-bottom: 1px solid #CCCCCC;
        color: #000000;
        font-size: 24px;
}
h3 {
        font-size: 18px;
}
h4 {
        font-size: 16px;
}
h5 {
        font-size: 14px;
}
h6 {
        color: #777777;
        background-color: inherit;
        font-size: 14px;
}
hr {
        height: 0.2em;
        border: 0;
        color: #CCCCCC;
        background-color: #CCCCCC;
display: inherit;
}
p, blockquote, ul, ol, dl, li, table, pre {
        margin: 15px 0;
}
a, a:visited {
        color: #4183C4;
        background-color: inherit;
        text-decoration: none;
}
#message {
        border-radius: 6px;
        border: 1px solid #ccc;
        display:block;
        width:100%;
        height:60px;
        margin:6px 0px;
}
button, #ws {
        font-size: 12 pt;
        padding: 4px 6px;
        border-radius: 5px;
        border: 1px solid #bbb;
        background-color: #eee;
}
code, pre, #ws, #message {
        font-family: Monaco;
        font-size: 10pt;
        border-radius: 3px;
        background-color: #F8F8F8;
        color: inherit;
}
code {
        border: 1px solid #EAEAEA;
        margin: 0 2px;
        padding: 0 5px;
}
pre {
        border: 1px solid #CCCCCC;
        overflow: auto;
        padding: 4px 8px;
}
pre > code {
        border: 0;
        margin: 0;
        padding: 0;
}
#ws { background-color: #f8f8f8; }
.bloop_markdown table {
border-collapse: collapse;
font-family: Helvetica, arial, freesans, clean, sans-serif;
color: rgb(51, 51, 51);
font-size: 15px; line-height: 25px;
padding: 0; }
.bloop_markdown table tr {
border-top: 1px solid #cccccc;
background-color: white;
margin: 0;
padding: 0; }
.bloop_markdown table tr:nth-child(2n) {
background-color: #f8f8f8; }
.bloop_markdown table tr th {
font-weight: bold;
border: 1px solid #cccccc;
margin: 0;
padding: 6px 13px; }
.bloop_markdown table tr td {
border: 1px solid #cccccc;
margin: 0;
padding: 6px 13px; }
.bloop_markdown table tr th :first-child, table tr td :first-child {
margin-top: 0; }
.bloop_markdown table tr th :last-child, table tr td :last-child {
margin-bottom: 0; }
.bloop_markdown blockquote{
border-left: 4px solid #dddddd;
padding: 0 15px;
color: #777777; }
blockquote > :first-child {
margin-top: 0; }
blockquote > :last-child {
margin-bottom: 0; }
code, pre, #ws, #message {
word-break: normal;
word-wrap: normal;
}
hr {
display: inherit;
}
.bloop_markdown :first-child {
-webkit-margin-before: 0;
}
code, pre, #ws, #message {
font-family: Menlo, Consolas, Liberation Mono, Courier, monospace;
}
.send { color:#77bb77; }
.server { color:#7799bb; }
.error { color:#AA0000; }</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class="bloop_markdown"><blockquote>
<p>I feel like <code>return</code> is very important part of <code>guard</code> statement.
I understand the requirement for consistency with
properties/closures/functions, but I’ll prefer to have some inconsistency
in language in this case and require <code>return</code> for <code>guard</code>. And in case I’ll
have to choose all-or-nothig, I’ll give –1 for the proposal. </p>
</blockquote>
<p>What’s the problem with single-expression guards? <code>guard</code> cannot fall trough and the type is inferred as the same as its parent closure has. </p>
<p>If we’d like to have this consistence everywhere in the language, <code>guards</code> will be part of that as well.</p>
<blockquote>
<p>I’d interpret that as being able to write:</p>
<pre><code class="swift">var x: Int8 { 20 }
as opposed to:
var x: Int8 { Int8(20) }
</code></pre>
</blockquote>
<p>Comment:</p>
<blockquote>
<p>Integer literals are untyped and pick up the type of their context.</p>
<p><a href="https://twitter.com/jckarter/status/649275500506955780">Joe Groff</a></p>
</blockquote>
<p>—</p>
<blockquote>
<p>Under “Proposed solution” you say (emphasis mine):</p>
<p>“Make return optional and infer return type for single-expressions everywhere in the language:”</p>
<p>However the return type isn’t inferred for computed properties or functions, and I don’t see type inference being discussed in the proposal (other than mentioning that closures have it). </p>
</blockquote>
<p>Is it worth discussing? I was using Brent’s words here, because my English isn’t that great:</p>
<blockquote>
<p>This actually doesn’t have anything to do with @autoclosure or @noescape. Any one-expression closure can omit the <code>return</code> statement and have <em>an inferred return type</em>. </p>
</blockquote>
<p>I could remove that from the proposal to sort out any confusion. It should be crystal clear that <code>return</code> should be optional for single-expressions.</p></div><div class="bloop_original_html"> <div id="bloop_sign_1464718846530487040" class="bloop_sign"><div style="font-family:helvetica,arial;font-size:13px">-- <br>Adrian Zubarev<br>Sent with Airmail</div></div></div><div class="bloop_markdown"><p></p></div><style>body{font-family:Helvetica,Arial;font-size:13px}</style></body></html>