<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><font color="#000000"><span style="background-color: rgba(255, 255, 255, 0);">On Nov 23, 2017, at 11:15 AM, Chris Lattner via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></span></font></div><blockquote type="cite"><font color="#000000"><span style="background-color: rgba(255, 255, 255, 0);">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><br></div><div>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><br></div><div>2. Code generation.</div><div><br></div><div>3. Windows-style paths. </div><div><br></div><div>4. Doesn’t LaTeX use backslashes?</div><div><br></div><div>5. Etc. </div><div><br></div><div>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><div id="AppleMailSignature"><div>-- </div><div>Brent Royal-Gordon</div>Sent from my iPhone</div><div><br></div></body></html>