<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"><p>Feel free to convince the core team to add such a list. ;)</p>
<p></p></div><div class="bloop_original_html"><style>body{font-family:Helvetica,Arial;font-size:13px}</style><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div> <br> <div id="bloop_sign_1464801909210979840" class="bloop_sign"><div style="font-family:helvetica,arial;font-size:13px">-- <br>Adrian Zubarev<br>Sent with Airmail</div></div> <br><p class="airmail_on">Am 1. Juni 2016 um 19:17:25, Vladimir.S (<a href="mailto:svabox@gmail.com">svabox@gmail.com</a>) schrieb:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>Do we have any 'feature' to not just throw away of proposals(and then scan
<br>mail list and remember), but put them in queue of proposals that should be
<br>reviewed after Swift 3 is released?
<br>
<br>Probably some list of such proposals on site, don't know. So I believe any
<br>proposal that would be raised now and got support from community - should
<br>be added to that queue on some page somewhere on swift.org
<br>
<br>On 01.06.2016 20:03, Adrian Zubarev via swift-evolution wrote:
<br>> Given that Swift 3 is winding down, we are in a mode of declining PRs
<br>> for proposals that don’t align with its goals. Please bring this back
<br>> up for discussion this fall, thanks for understanding.
<br>>
<br>> Closed by Chris. Sad but we’ll have to wait a little longer for this change.
<br>>
<br>>
<br>>
<br>> --
<br>> Adrian Zubarev
<br>> Sent with Airmail
<br>>
<br>> Am 1. Juni 2016 um 06:58:27, Thorsten Seitz (tseitz42@icloud.com
<br>> <mailto:tseitz42@icloud.com>) schrieb:
<br>>
<br>>> +1
<br>>>
<br>>> `return` in guards should stay, because there one has to use either
<br>>> `return`, `continue` or `break`. It would be ugly and inconsistent if one
<br>>> of these could be left out.
<br>>>
<br>>> -Thorsten
<br>>>
<br>>> > Am 31.05.2016 um 20:16 schrieb Vladimir.S via swift-evolution <swift-evolution@swift.org>:
<br>>> >
<br>>> > I really like the proposal in case of properties and functions, but I really don't want to have
<br>>> > guard boolean else { "false" }
<br>>> >
<br>>> > I feel like `return` is very important part of `guard` statement.
<br>>> > 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 `return` for `guard`. And in case I'll have to choose all-or-nothig, I'll give -1 for the proposal.
<br>>> >
<br>>> > I.e. IMO current `return` in properties and functions is less evil than absent of `return` in `guard`.
<br>>> >
<br>>> >> On 31.05.2016 20:35, Adrian Zubarev via swift-evolution wrote:
<br>>> >> Here is the draft proposal:
<br>>> >> https://github.com/DevAndArtist/swift-evolution/blob/single_expression_optional_return/proposals/nnnn-single-expression-optional-return.md
<br>>> >>
<br>>> >> Did I covered everything case? If you find some mistakes feel free to
<br>>> >> provide feedback so I can fix the proposal before I submit a PR.
<br>>> >>
<br>>> >>
<br>>> >>
<br>>> >> --
<br>>> >> Adrian Zubarev
<br>>> >> Sent with Airmail
<br>>> >>
<br>>> >> Am 31. Mai 2016 um 18:33:09, Leonardo Pessoa via swift-evolution
<br>>> >> (swift-evolution@swift.org <mailto:swift-evolution@swift.org>) schrieb:
<br>>> >>
<br>>> >>> +1
<br>>> >>>
<br>>> >>> L
<br>>> >>>
<br>>> >>> On 31 May 2016 at 12:47, Matthew Johnson via swift-evolution
<br>>> >>> <swift-evolution@swift.org> wrote:
<br>>> >>> >
<br>>> >>> >> On May 28, 2016, at 3:09 AM, David Hart via swift-evolution <swift-evolution@swift.org> wrote:
<br>>> >>> >>
<br>>> >>> >> It isn’t a special case because all other single-statement closures in the language work that way. It’s actually inconsistent now.
<br>>> >>> >
<br>>> >>> > Computed properties aren’t closures so it’s not inconsistent in that sense. But it is inconsistent in that closures are the *only* value-returning code blocks that are able to use this sugar. It would be nice to see this sugar consistently allowed everywhere in the language.
<br>>> >>> >
<br>>> >>> >>
<br>>> >>> >>> On 28 May 2016, at 09:03, Brian Christensen via swift-evolution <swift-evolution@swift.org> wrote:
<br>>> >>> >>>
<br>>> >>> >>> On May 27, 2016, at 13:57, Adrian Zubarev via swift-evolution <swift-evolution@swift.org> wrote:
<br>>> >>> >>>
<br>>> >>> >>>> The idea is simple:
<br>>> >>> >>>>
<br>>> >>> >>>> • Can we make return keyword optional in cases like this?
<br>>> >>> >>>> • Shouldn’t this behave like @autoclosure or @noescape?
<br>>> >>> >>>> type A {
<br>>> >>> >>>> var characters: [Character] = …
<br>>> >>> >>>> var string: String { String(self.characters) }
<br>>> >>> >>>> var count: Int { 42 }
<br>>> >>> >>>> }
<br>>> >>> >>>>
<br>>> >>> >>>> Is this worth a proposal or Swifty enough, what do you think?
<br>>> >>> >>>>
<br>>> >>> >>>> Sure I could write return, but why do we allow this behavior for @noescape functions like map!?
<br>>> >>> >>>
<br>>> >>> >>> While I am not necessarily against this idea, I do wonder if it’s worth making what’s going on here less obvious simply for the sake of being able to omit a six character keyword. As I understand it, one of the reasons ++/-- were removed was due to the increased "burden to learn Swift as a first programming language.” This is the sort of thing that becomes another one of those special cases that has to be explained to someone new to Swift.
<br>>> >>> >>>
<br>>> >>> >>> /brian
<br>>> >>> >>>
<br>>> >>> >>> _______________________________________________
<br>>> >>> >>> swift-evolution mailing list
<br>>> >>> >>> swift-evolution@swift.org
<br>>> >>> >>> https://lists.swift.org/mailman/listinfo/swift-evolution
<br>>> >>> >>
<br>>> >>> >> _______________________________________________
<br>>> >>> >> swift-evolution mailing list
<br>>> >>> >> swift-evolution@swift.org
<br>>> >>> >> https://lists.swift.org/mailman/listinfo/swift-evolution
<br>>> >>> >
<br>>> >>> > _______________________________________________
<br>>> >>> > swift-evolution mailing list
<br>>> >>> > swift-evolution@swift.org
<br>>> >>> > https://lists.swift.org/mailman/listinfo/swift-evolution
<br>>> >>> _______________________________________________
<br>>> >>> swift-evolution mailing list
<br>>> >>> swift-evolution@swift.org
<br>>> >>> https://lists.swift.org/mailman/listinfo/swift-evolution
<br>>> >>
<br>>> >>
<br>>> >>
<br>>> >> _______________________________________________
<br>>> >> swift-evolution mailing list
<br>>> >> swift-evolution@swift.org
<br>>> >> https://lists.swift.org/mailman/listinfo/swift-evolution
<br>>> > _______________________________________________
<br>>> > swift-evolution mailing list
<br>>> > swift-evolution@swift.org
<br>>> > https://lists.swift.org/mailman/listinfo/swift-evolution
<br>>
<br>>
<br>>
<br>> _______________________________________________
<br>> swift-evolution mailing list
<br>> swift-evolution@swift.org
<br>> https://lists.swift.org/mailman/listinfo/swift-evolution
<br>>
<br></div></div></span></blockquote></div><div class="bloop_markdown"><p></p></div></body></html>