<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="">Renamed subject - going forward.<div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 2016-01-19, at 5:53:57, Craig Cruden <<a href="mailto:ccruden@novafore.com" class="">ccruden@novafore.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="">I have renamed the document - new link is<div class=""><br class=""></div><div class=""><a href="https://github.com/cacruden/swift-evolution/blob/master/proposals/0023-Pattern-Matching-Partial-Function.md" class="">https://github.com/cacruden/swift-evolution/blob/master/proposals/0023-Pattern-Matching-Partial-Function.md</a></div><div class=""><br class=""></div><div class="">I have initiated a pull request…. I think the proposal is sufficient to get to the review stage (which is a week)… so the haggling on the small stuff will likely happen again at that time anyway.</div><div class=""><br class=""></div><div class="">Of course my views may be corrupted by being too close to the proposal :p</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div class=""><blockquote type="cite" class=""><div class="">On 2016-01-18, at 3:04:35, Charles Constant <<a href="mailto:charles@charlesism.com" class="">charles@charlesism.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra">I think examples are convincing, but ideally we would put most of them in separate document. </div><div class="gmail_extra"><br class=""></div><div class="gmail_extra">Though I love reading about programming, I generally do it in a half-assed sort of way. Unless the writing is very blunt and clear, I don't really understand it until I need to do it myself. I doubt I'm the only person here like this. <br class=""></div><div class="gmail_extra"><br class=""></div><div class="gmail_extra">I badly want this proposal to gain traction (more so every time I find myself writing code that it could improve, which happens daily). I think the proposal ought to be short and sweet. I believe if we hold the reader's attention just long enough for them to understand what we're talking about, they'll be onboard. Once they're hooked, we have our second document with the list of examples.</div><div class="gmail_extra"><br class=""></div><div class="gmail_extra">It would also be great to have the "before snippet" and "after snippet" visually arranged side-by-side. I'm guessing markdown doesn't support this :(</div><div class="gmail_extra"><br class=""></div><div class="gmail_extra"><br class=""></div></div>
</div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></body></html>