<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Nov 23, 2017, at 11:10 AM, Brent Royal-Gordon <<a href="mailto:brent@architechies.com" class="">brent@architechies.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class=""><font class=""><span style="background-color: rgba(255, 255, 255, 0);" class="">On Nov 23, 2017, at 11:15 AM, Chris Lattner via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><br class=""></span></font></div><blockquote type="cite" class=""><font class=""><span style="background-color: rgba(255, 255, 255, 0);" class="">Until we figure out that path forward for regex’s, I think they aren’t the right motivation for this proposal.</span></font></blockquote><div class=""><br class=""></div><div class="">1. Even in our shining pattern matching future—a future which I, for one, am eager to hasten—we will still need to interoperate with NSRegularExpression and other Perl 5-compatible regex engines.</div></div></div></blockquote><div><br class=""></div><div>We already interoperate with those other engines. When we have an awesome default answer, I don’t see why we’d be compelled to sugar them any more.</div><div><br class=""></div><blockquote type="cite" class=""><div class=""><div dir="auto" class=""><div class="">2. Code generation.</div><div class=""><br class=""></div><div class="">3. Windows-style paths. </div><div class=""><br class=""></div><div class="">4. Doesn’t LaTeX use backslashes?</div></div></div></blockquote><div><br class=""></div><div>Right, I’m only objecting to regex as the motivation.</div><div><br class=""></div><div>-Chris</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div dir="auto" class=""><div class=""><br class=""></div><div class="">5. Etc. </div><div class=""><br class=""></div><div class="">I think the Motivation section undersells this proposal. Regexes are a strong short-run use case, but in the long run, we’ll need this for other things. In both cases, though, raw literals will be a useful addition to the language, improving the clarity of Swift code much like multiline literals already have. </div><br class=""><div class=""><div class="">-- </div><div class="">Brent Royal-Gordon</div>Sent from my iPhone</div><div class=""><br class=""></div></div></div></blockquote></div><br class=""></body></html>