<div dir="ltr">Side question: it looks like ICU is used by the standard library on non-Apple platforms. Would it be possible to make it a dependency of the compiler too? If we want to explicitly detect emoji, for instance, it'd be nice to use a canonical library that already does it.<div class="gmail_extra">
<br><div class="gmail_quote">On Sun, Sep 18, 2016 at 12:33 PM, Jacob Bandes-Storch <span dir="ltr"><<a href="mailto:jtbandes@gmail.com" target="_blank">jtbandes@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div dir="ltr"><div><div><b>TL;DR:</b></div><div><br></div><div>Swift 4 Stage 1 seeks to prioritize "Source stability features". Most source-breaking changes were done with in Swift 3; however, the categorization of Unicode characters into identifiers & operators was never thoroughly discussed on swift-evolution. This seems like it might be our last chance, and I think there are some big improvements to be had.</div><div><br></div><div>I've gathered some information+thoughts into an early-stage pitch / pre-proposal. It doesn't really have a conclusion, so I'm hoping we can discuss these issues and come up with good (pragmatic) solutions here. I imagine this can morph into a proposal later.</div><div><br></div><div>You can read the following in nicer HTML form at <a href="https://gist.github.com/jtbandes/c0b0c072181dcd22c3147802025d0b59" target="_blank">https://gist.github.com/<wbr>jtbandes/<wbr>c0b0c072181dcd22c3147802025d0b<wbr>59</a></div><div><br>I look forward to the discussion!<br></div><div><br></div><div>-Jacob</div><div><snip></div></div></div></div></div></div></blockquote></div></div></div>