<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I know that the overall goal of the proposal is to keep it short, but I am wondering if maybe an appendix with quite a few examples of before and after would be useful. It may be hard to see how this improves things until you see it in practice. <div class=""><br class=""></div><div class="">- Paul </div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 17, 2016, at 9:16 AM, Craig Cruden via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">There were about 10 postings today about the integrating the proposed updated version of the motivation section. The introduction makes clear the proposal is for a generalized way of writing unary functions. The motivation behind the proposal was primarily driven by the map implementation of it, but at the end it leads back to a generalized version being able to be used with reduce (including examples). <div class=""><br class=""></div><div class="">I won’t get around to thinking about it until tomorrow though.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 2016-01-18, at 0:00:59, Thorsten Seitz <<a href="mailto:tseitz42@icloud.com" class="">tseitz42@icloud.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Maybe I misread your proposed beginning, but the proposal should not be about introducing a new map method. <div class="">It introduces a new way of writing unary closures (i.e. closures taking one argument) with case clauses, i.e<div class=""><br class=""></div><div class="">instead of having to write</div><div class=""><br class=""></div><div class="">{ x in </div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>switch x {</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>case .Cold: return „Too cold“</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>case .Hot: return „Too hot“</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>default: return „Just right“</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>}</div><div class="">}</div><div class=""><br class=""></div><div class="">we could just write</div><div class=""><br class=""></div><div class=""><div class="">{ <span class="Apple-tab-span" style="white-space: pre;"> </span></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>case .Cold: „Too cold“</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>case .Hot: „Too hot“</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>default: „Just right“</div><div class="">}</div><div class=""><br class=""></div><div class="">The case clauses may (or must?) be expressions instead of statements.</div><div class=""><br class=""></div><div class="">This will work with any higher order function, not just map, as the result is just a normal closure. No special version of „map“ needed.</div><div class=""><br class=""></div><div class="">-Thorsten</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div class=""><blockquote type="cite" class=""><div class="">Am 17.01.2016 um 13:37 schrieb Charles Constant via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>>:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">It's better, but it still seems a bit dry to me. I tried rewriting the beginning. Is it better to start off like this?</div><div class=""><br class=""></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px" class=""><div class=""><div class=""><i class="">We are proposing a new “map” method. It directly addresses a “mapping” problem that pops up in almost all Swift programs, and currently has no elegant solution. The syntax we propose makes Swift code easier to read, easier to write, and less buggy.</i></div></div><div class=""><div class=""><i class=""><br class=""></i></div></div><div class=""><div class=""><i class="">Here is an example of the problem, where we want to assign a string mapped to an enum case:</i></div></div><div class=""><div class=""><i class=""><br class=""></i></div></div><div class=""><div class=""><i class=""><span class="" style="white-space:pre"> </span>let str:String</i></div></div><div class=""><div class=""><span class="" style="white-space:pre"><i class=""> </i></span></div></div><div class=""><div class=""><i class=""><span class="" style="white-space:pre"> </span>switch state {</i></div></div><div class=""><div class=""><i class=""><span class="" style="white-space:pre"> </span>case .Cold: </i></div></div><div class=""><div class=""><i class=""><span class="" style="white-space:pre"> </span>str = “Too cold”</i></div></div><div class=""><div class=""><i class=""><span class="" style="white-space:pre"> </span>case .Hot: </i></div></div><div class=""><div class=""><i class=""><span class="" style="white-space:pre"> </span>str = “Too hot”</i></div></div><div class=""><div class=""><i class=""><span class="" style="white-space:pre"> </span>default: </i></div></div><div class=""><div class=""><i class=""><span class="" style="white-space:pre"> </span>str = “Just right”</i></div></div><div class=""><div class=""><i class=""><span class="" style="white-space:pre"> </span>}</i></div></div><div class=""><div class=""><i class=""><br class=""></i></div></div><div class=""><div class=""><i class="">The syntax above does not elegantly express our intent. The “switch” statement is designed for “flow control”, but aside from choosing a single value, our example needs no “flow control”. Moreover, the ability to execute unrelated statements inside the “switch” encourages buggy code. Use of the “switch” statement for this task leads to bloated, confusing, error-prone code.</i></div></div></blockquote><div class=""><br class=""></div><div class="">Do you like it? It's all pretty subjective, I suppose.</div><div class=""><br class=""></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Sat, Jan 16, 2016 at 8:51 PM, Craig Cruden <span dir="ltr" class=""><<a href="mailto:ccruden@novafore.com" target="_blank" class="">ccruden@novafore.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word" class="">Forgot to include the link so people don’t need to search:<div class=""><br class=""></div><div class=""><a href="https://github.com/cacruden/swift-evolution/blob/master/proposals/0000-Pattern-Matching-Partial-Function.md" target="_blank" class="">https://github.com/cacruden/swift-evolution/blob/master/proposals/0000-Pattern-Matching-Partial-Function.md</a></div><div class=""><div class="h5"><div class=""><br class=""></div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 2016-01-17, at 11:43:39, Craig Cruden <<a href="mailto:ccruden@novafore.com" target="_blank" class="">ccruden@novafore.com</a>> wrote:</div><br class=""><div class=""><div style="word-wrap:break-word" class="">Updated the the motivation clause - not sure I am 100% there yet - but hopefully closer. <div class=""><br class=""></div><div class="">As well as a few minor updates to things like let on reduce example and clarifying that the partial closures can use the optional return keyword.</div><div class=""><br class=""></div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 2016-01-15, at 4:16:56, Charles Constant <<a href="mailto:charles@charlesism.com" target="_blank" class="">charles@charlesism.com</a>> wrote:</div><br class=""><div class=""><div dir="ltr" class="">Hi Craig,<div class=""><br class=""></div><div class="">Well done, what you wrote looks pretty good to me. I had no trouble understanding the proposal. It's a good length, too - I think the shorter we can make it, the more appealing it is. </div><div class=""><br class=""></div><div class="">The only section that I think needs improvement is "Motivation." I think we could sell it better. I know when I've read some of the other proposals, I do it in fairly cursory way.</div><div class="">"Motivation" could be clearer for those of our peers who haven't followed the thread. <br class=""></div><div class=""><br class=""></div><div class="">The motivation, from my point of view:</div><div class="">- the need to use a value from one domain, as a "key" to another is very common. The ternary is a special case of this, and for all it's flaws, it's a very popular expression in multiple languages </div><div class="">- using the existing "switch" to do this is bloated (more so in Swift because you have to declare the variable before the switch statement)</div><div class="">- using the existing "switch" to do this is less safe, because unrelated code can be inserted in the case statements<br class=""></div><div class="">- current alternatives to "switch" aren't good (e.g.: using a Dict has quirks that add the cognitive load)</div><div class="">- this new "map" method can make code less verbose, easier to read, and safer</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, Jan 14, 2016 at 11:23 AM, Craig Cruden <span dir="ltr" class=""><<a href="mailto:ccruden@novafore.com" target="_blank" class="">ccruden@novafore.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><div class="">Paul, </div><div class=""><br class=""></div>I tried to put my understanding on the latest proposal option into a draft on github (instead of my usual BitBucket repo). <div class=""><br class=""></div><div class="">Take a look at it and see if there is anything useable.</div><div class=""><br class=""></div><div class=""><a href="https://github.com/cacruden/swift-evolution/blob/master/proposals/0000-Pattern-Matching-Partial-Function.md" target="_blank" class="">https://github.com/cacruden/swift-evolution/blob/master/proposals/0000-Pattern-Matching-Partial-Function.md</a></div><span class=""><font color="#888888" class=""><div class=""><br class=""></div><div class="">Craig</div></font></span><div class=""><div class=""><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 2016-01-11, at 14:17:09, Craig Cruden <<a href="mailto:ccruden@novafore.com" target="_blank" class="">ccruden@novafore.com</a>> wrote:</div><br class=""><div class=""><div style="word-wrap:break-word" class="">Ignore the last comment - tired and mistaken. :p<div class=""><br class=""></div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 2016-01-11, at 14:16:01, Craig Cruden <<a href="mailto:ccruden@novafore.com" target="_blank" class="">ccruden@novafore.com</a>> wrote:</div><br class=""><div class=""><div style="word-wrap:break-word" class="">I just realized “cases” probably is not needed - if it see’s a comma after case but before “:” then it is the concise form. <div class=""><br class=""></div><div class="">If the switch / case can do that , the partial function case should be able to do the same thing.</div><div class=""><br class=""></div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 2016-01-11, at 13:23:19, Craig Cruden <<a href="mailto:ccruden@novafore.com" target="_blank" class="">ccruden@novafore.com</a>> wrote:</div><br class=""><div class=""><div style="word-wrap:break-word" class=""><div class="">I have thought about it a bit more and I think this would cover all the cases that interest me (in addition to others needs for a little more conciseness on the most simple case). </div><div class=""><br class=""></div><div class="">I also think we need to be clear that the “case” (or cases) and “default” are is really just a partial function which in it’s entirety is really just a complete function for used wherever a complete function (exhaustive) can be passed (e.g. reduce, filter, etc.) - otherwise they might get confused on why we are adding it to “map”. </div><div class=""><br class=""></div><div class="">The optional where clause should also be part of the case clause as part of the proposal. </div><div class=""><br class=""></div><div class="">There would be no need for statement based “fallthrough”.</div><div class=""><br class=""></div><div class="">You mentioned your proposal…. have you drafted a formal proposal draft?</div><div class=""><br class=""></div><div class=""><br class=""></div><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 2016-01-10, at 12:41:03, Paul Ossenbruggen via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>> wrote:</div><br class=""><div class="">I agree that it would be really useful to keep things concise. I am going to suggest again an idea I had in the past, it is also in my proposal, which might work well for this problem. This might address the verbosity of the “case” and at the same time make it obvious we are dealing with a switch expression. So both would be valid: <div class=""><br class=""></div><div class=""><div class=""><div dir="ltr" class=""><div style="word-wrap:break-word" class=""><div dir="ltr" class=""><div style="word-wrap:break-word" class=""><div dir="ltr" class=""><div style="font-size:13px;margin:0px;line-height:normal;font-family:Arial" class=""><b class=""><div dir="ltr" style="font-family:Helvetica;font-size:12px;font-weight:normal" class=""><div style="word-wrap:break-word" class=""><div dir="ltr" class=""><div style="word-wrap:break-word" class=""><div dir="ltr" class=""><b style="font-family:Arial;font-size:13px" class=""><b class=""><span style="color:rgb(96,96,96);white-space:pre-wrap" class=""> </span><font color="#006d8f" class="">let</font></b><b style="color:rgb(96,96,96)" class=""> num = color.</b><font color="#008cb4" class="">map </font>{</b></div></div></div></div></div></b></div></div></div></div></div></div></div></div></div></blockquote><blockquote type="cite" class=""><b style="font-family:Arial;font-size:13px" class=""><b style="color:rgb(96,96,96)" class=""><span style="white-space:pre-wrap" class=""> </span></b><b class=""><span style="white-space:pre-wrap" class=""><font color="#606060" class=""> </font><font color="#006d8f" class="">cases</font><font color="#606060" class=""> </font></span></b><b class=""><font color="#4f7a28" class="">.Red:</font></b><b style="color:rgb(227,36,0)" class=""> </b><b style="color:rgb(96,96,96)" class="">100,</b><b style="color:rgb(96,96,96)" class=""> </b></b><br class=""><b style="font-family:Arial;font-size:13px" class=""><b style="color:rgb(96,96,96)" class=""><span style="white-space:pre-wrap" class=""> </span></b><b class=""><span style="white-space:pre-wrap" class=""><font color="#606060" class=""> <span style="white-space:pre-wrap" class=""> </span> </font><font color="#4f7a28" class="">.</font></span></b><b class=""><font color="#4f7a28" class="">Green: </font></b><span class=""> </span><b style="color:rgb(96,96,96)" class="">200</b><b class=""><font color="#e32400" class="">,</font></b><b style="color:rgb(96,96,96)" class=""> </b></b><br class=""><b style="font-family:Arial;font-size:13px" class=""><b style="color:rgb(96,96,96)" class=""><span style="white-space:pre-wrap" class=""> </span></b><b style="color:rgb(96,96,96)" class=""><span style="white-space:pre-wrap" class=""> <span style="white-space:pre-wrap" class=""> </span> </span></b><b class=""><font color="#4f7a28" class="">.Blue</font><font color="#e32400" class="">: </font></b><b style="color:rgb(96,96,96)" class="">300</b></b><br class=""><b style="font-family:Arial;font-size:13px" class=""><b style="color:rgb(96,96,96)" class=""><span style="white-space:pre-wrap" class=""> </span></b><b class=""><span style="white-space:pre-wrap" class=""><font color="#606060" class=""> </font><font color="#006d8f" class="">default</font></span></b><b style="color:rgb(227,36,0)" class="">: </b><b style="color:rgb(96,96,96)" class="">-1</b><b style="color:rgb(227,36,0)" class=""> </b></b><br class=""><b style="font-family:Arial;font-size:13px" class=""><span style="color:rgb(227,36,0);white-space:pre-wrap" class=""> </span>}</b><br class=""><b style="font-family:Arial;font-size:13px" class=""><b class=""><span style="color:rgb(96,96,96);white-space:pre-wrap" class=""> </span><font color="#006d8f" class="">let</font></b><b style="color:rgb(96,96,96)" class=""> num = color.</b><b class=""><font color="#008cb4" class="">map </font>{</b></b><br class=""><b style="font-family:Arial;font-size:13px" class=""><b style="color:rgb(96,96,96)" class=""><span style="white-space:pre-wrap" class=""> </span></b><b class=""><span style="white-space:pre-wrap" class=""><font color="#606060" class=""> </font><font color="#006d8f" class="">case</font><font color="#606060" class=""> </font></span></b><b class=""><font color="#4f7a28" class="">.Red:</font></b><b style="color:rgb(227,36,0)" class=""> </b><b style="color:rgb(96,96,96)" class="">100</b></b><br class=""><b style="font-family:Arial;font-size:13px" class=""><b style="color:rgb(96,96,96)" class=""><span style="white-space:pre-wrap" class=""> </span></b><b class=""><span style="white-space:pre-wrap" class=""><font color="#606060" class=""> </font><font color="#006d8f" class="">case </font><font color="#606060" class=""> </font><font color="#4f7a28" class="">.</font></span></b><b class=""><font color="#4f7a28" class="">Green: </font></b><span style="font-family:Helvetica" class=""> </span><b style="color:rgb(96,96,96)" class="">200</b><b style="color:rgb(96,96,96)" class=""> </b></b><br class=""><b style="font-family:Arial;font-size:13px" class=""><b style="color:rgb(96,96,96)" class=""><span style="white-space:pre-wrap" class=""> </span></b><b class=""><span style="white-space:pre-wrap" class=""><font color="#606060" class=""> </font><font color="#006d8f" class="">case</font><font color="#606060" class=""> </font></span></b><b class=""><font color="#4f7a28" class="">.Blue</font><font color="#e32400" class="">: </font></b><b style="color:rgb(96,96,96)" class="">300</b></b><br class=""><b style="font-family:Arial;font-size:13px" class=""><b style="color:rgb(96,96,96)" class=""><span style="white-space:pre-wrap" class=""> </span></b><b class=""><span style="white-space:pre-wrap" class=""><font color="#606060" class=""> </font><font color="#006d8f" class="">default</font></span></b><b style="color:rgb(227,36,0)" class="">: </b><b style="color:rgb(96,96,96)" class="">-1</b><b style="color:rgb(227,36,0)" class=""> </b></b><br class=""><div style="word-wrap:break-word" class=""><div class=""><div class=""><div class=""><div class=""><div style="word-wrap:break-word" class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div style="word-wrap:break-word" class=""><div class=""><div class=""><div class=""><div dir="ltr" class=""><div style="word-wrap:break-word" class=""><div dir="ltr" class=""><div style="word-wrap:break-word" class=""><div dir="ltr" class=""><div style="font-size:13px;margin:0px;line-height:normal;font-family:Arial" class=""><b class=""><span style="color:rgb(227,36,0);white-space:pre-wrap" class=""> </span>}</b></div><div class=""><b class=""><br class=""></b></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></blockquote></div><br class=""></div></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></div></div></div></blockquote></div><br class=""></div>
</div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></div></div></div></blockquote></div><br class=""></div></div>
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div></blockquote></div><br class=""></div></div></div></div></div></blockquote></div><br class=""></div></div>_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></div></body></html>