<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=""><blockquote type="cite" class="">It had the idea that maybe the motivation behind continuation quotes is to make using multiline strings harder to use; in order to discourage their use at all.<br class=""></blockquote><br class="">Absolutely not, and frankly I resent the implication.<br class=""><br class="">I'm looking at a space where (in my opinion) all existing designs are ugly and inelegant and trying to find something better. There are *reasons* Swift 2 doesn't allow newlines in quote marks; I'm trying to address them, not ignore them. There are nasty formatting problems; I'm trying to solve them, not tolerate them. There are significant context-sensitivity issues; I'm trying to fix them, not punt the problem to a syntax highlighter that is absent or incorrect in half of our tools.<br class=""><br class="">Here's a piece of code-generating code I once wrote, ported to this prototype:<br class=""><br class=""><span class="Apple-tab-span" style="white-space:pre">        </span><a href="https://gist.github.com/brentdax/8a8ee1f6028230f68ed85b7f3ebc95bf" class="">https://gist.github.com/brentdax/8a8ee1f6028230f68ed85b7f3ebc95bf</a><br class=""><br class="">(The actual code generation starts on line 93.) <br class=""><br class="">And here's the same code in (beta-era) Swift 2:<br class=""><br class=""><span class="Apple-tab-span" style="white-space:pre">        </span>https://github.com/brentdax/WebResponder/blob/master/WebResponderCore/WebResponderCore/codes2swift.swift<br class=""><br class="">I think the new version is an improvement over the old. I think I like it better than I would with `"""` or heredocs forcing things against the left margin. I think it's nice that I can look at any line—out of context, random access—and see which parts are string literals. I think if I want to add a doc comment to each of the constants it generates, I have to do a little awkward code shuffling, but the result is worth it:<br class=""><br class=""><font face="Menlo" class=""><span class="Apple-tab-span" style="white-space:pre">        </span>for statusLine in statusLines {<br class=""><span class="Apple-tab-span" style="white-space:pre">        </span> code += " /// The HTTP \(statusLine.code) \(statusLine.message) status, used with `HTTPResponseType.status`.<br class=""><span class="Apple-tab-span" style="white-space:pre">        </span> " \(statusLine.constant)</font><div class=""><div class=""><font face="Menlo" class=""><span class="Apple-tab-span" style="white-space:pre">        </span> " </font></div><font face="Menlo" class=""><span class="Apple-tab-span" style="white-space:pre">        </span> ""<br class=""><span class="Apple-tab-span" style="white-space:pre">        </span>}<br class=""><br class=""></font>Overall, I find this code a lot more pleasant to read than it was in Swift 2, and somewhat more pleasant than it would be with `"""` or a heredoc. Maybe you don't agree; maybe you'd rather import some other language's warts. I understand—those warts come with convenience advantages, and you might prefer that convenience to the other things.</div><div class=""><br class=""></div><div class="">But at least have the basic respect for opposing viewpoints not to impugn my motives because you disagree with me or don't like what I suggest. That is just not nice.</div><div class=""><br class=""><div class="">-- <br class="">Brent Royal-Gordon<br class="">Architechies<br class=""></div><br class=""></div></body></html>