<div dir="ltr">I imagine you can use a combination of:<div><br></div><div><b>Deferred for Future Discussion</b>:<br><div> <a href="https://github.com/apple/swift-evolution#deferred-for-future-discussion">https://github.com/apple/swift-evolution#deferred-for-future-discussion</a><div><b>Accepted proposals which do not have a complete implementation:<br></b><div> <a href="https://github.com/apple/swift-evolution#accepted-proposals-which-do-not-have-a-complete-implementation">https://github.com/apple/swift-evolution#accepted-proposals-which-do-not-have-a-complete-implementation</a></div><div><b>Pull requests:</b></div></div></div></div><div> <a href="https://github.com/apple/swift-evolution/pulls">https://github.com/apple/swift-evolution/pulls</a><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 2, 2016 at 3:25 AM, Adrian Zubarev via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> 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"><div><p>Feel free to convince the core team to add such a list. ;)</p>
<p></p></div><div><span class=""><div style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div> <br> <div><div style="font-family:helvetica,arial;font-size:13px">-- <br>Adrian Zubarev<br>Sent with Airmail</div></div> <br></span><div><div class="h5"><p>Am 1. Juni 2016 um 19:17:25, Vladimir.S (<a href="mailto:svabox@gmail.com" target="_blank">svabox@gmail.com</a>) schrieb:</p> <blockquote type="cite"><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 <a href="http://swift.org" target="_blank">swift.org</a>
<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 (<a href="mailto:tseitz42@icloud.com" target="_blank">tseitz42@icloud.com</a>
<br>> <mailto:<a href="mailto:tseitz42@icloud.com" target="_blank">tseitz42@icloud.com</a>>) 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 <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>>:
<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>>> >> <a href="https://github.com/DevAndArtist/swift-evolution/blob/single_expression_optional_return/proposals/nnnn-single-expression-optional-return.md" target="_blank">https://github.com/DevAndArtist/swift-evolution/blob/single_expression_optional_return/proposals/nnnn-single-expression-optional-return.md</a>
<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>>> >> (<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a> <mailto:<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>>) schrieb:
<br>>> >>
<br>>> >>> +1
<br>>> >>>
<br>>> >>> L
<br>>> >>>
<br>>> >>> On 31 May 2016 at 12:47, Matthew Johnson via swift-evolution
<br>>> >>> <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:
<br>>> >>> >
<br>>> >>> >> On May 28, 2016, at 3:09 AM, David Hart via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> 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 <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:
<br>>> >>> >>>
<br>>> >>> >>> On May 27, 2016, at 13:57, Adrian Zubarev via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> 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>>> >>> >>> <a href="mailto: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>>> >>> >>
<br>>> >>> >> _______________________________________________
<br>>> >>> >> swift-evolution mailing list
<br>>> >>> >> <a href="mailto: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>>> >>> >
<br>>> >>> > _______________________________________________
<br>>> >>> > swift-evolution mailing list
<br>>> >>> > <a href="mailto: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>>> >>> _______________________________________________
<br>>> >>> swift-evolution mailing list
<br>>> >>> <a href="mailto: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>>> >>
<br>>> >>
<br>>> >>
<br>>> >> _______________________________________________
<br>>> >> swift-evolution mailing list
<br>>> >> <a href="mailto: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>>> > _______________________________________________
<br>>> > swift-evolution mailing list
<br>>> > <a href="mailto: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>>
<br>>
<br>>
<br>> _______________________________________________
<br>> swift-evolution mailing list
<br>> <a href="mailto: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>>
<br></div></div></span></blockquote></div></div></div><div><p></p></div></div><br>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br></blockquote></div><br></div>