<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=""><div class="">@1: Or Xcode could simply continue the string if you hit enter without terminating it. (Same if you open a string literal, and then paste a multiline text)</div><div class="">To copy out of Xcode, use alt-click selection to cut away leading ".</div><div class=""><br class=""></div><div class="">@2: +1</div><div class=""><br class=""></div><div class="">@3: +1. Don't see the point why this should be better than simply adding strings up with +.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Generally, I'm kind of sceptical about this. Especially trailing whitespace becomes invisible.</div><div class="">You don't know if your editor cuts out trailing whitespace. You no longer see where each line ends.</div><div class=""><br class=""></div><div class="">Maybe with Xcode, the IDE could display kind of a rectangle that shows what's the left / right border of each line </div><div class="">(maybe background color the parts that are within the string, so you actually see trailing whitespace).</div><div class=""><br class=""></div><div class="">Still, even then I fail to see the real need for multiline string literals if you assume that your IDE is smart enough</div><div class="">to detect whether you are editing a string, and to automatically insert the <b class="">" + </b> on the current line and the <b class=""><i class="">indentation</i></b> <b class="">"</b> on the next line</div><div class="">when you press enter or paste a multiline text in that context.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">-1 for Heredoc proposal. It's just ugly, and even in languages that have it (e.g. PHP) I've never seen it used in current code,</div><div class="">with the exception of XML (where it's the only option I guess).</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">As for escaping vs non-escaping, just adding a few other languages as reference.</div><div class=""><br class=""></div><div class="">PHP uses " ... " to denote strings with interpolation and \n transformation etc., and ' ... ' for verbatim strings.</div><div class="">C# uses " ... " for normal strings and @" ... " for verbatim strings (e.g. Windows paths that incorporate lots of \).</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Etan</div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On 14 Dec 2015, at 23:21, Andrey Tarantsov via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</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=""><div class=""><blockquote type="cite" class=""><div class=""><div class="">Yes, you are right, Brent, there should be a closing quote on the last line otherwise it would be a syntax error. That’s a much better idea! That would also fix the <br class=""><br class="">let x = “foo<br class=""><br class="">being valid syntax problem.<br class=""></div></div></blockquote></div><div class=""><br class=""></div><div class="">Guys, you know this is crazy, right? :-)</div><div class=""><br class=""></div><div class="">1) copy & paste would be really annoying (on that note, Xcode should totally get multiple cursors support like in Sublime)</div><div class=""><br class=""></div><div class="">2) any non-specialized syntax highlighter would parse them all completely incorrectly, which is not a show-stopper, but shouldn't be taken lightly. (Think a generic indented code block in Markdown on GitHub.)</div><div class=""><br class=""></div><div class="">3) it's just cruel — <a href="https://xkcd.com/859/" class="">https://xkcd.com/859/</a></div><div class=""><br class=""></div><span id="cid:A640DCFD-3F56-4764-A630-99C46837109E"><(.png></span><br class=""><div class=""><br class=""></div><div class="">A.</div><div class=""><br class=""></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=tTTJ5sn5y0uc3ODSZa-2BndLNwXCDS7T2cq5OlDDhG0RuTSEOeVK4NjT7DoOvgvzuZitqSuFLsqqakjVMsFRW6YMphUcKMOgXjZ-2F6ljqndZnloEqZJPAw0-2BtCn7rX5ilf4-2B3amByYfelNkHWnVa-2Bw-2FMd-2BYuMETtpQ1vKfkhqpPDUyojamlCnndlfYFGmBTQkzTaHuwgHmkgfURCyMwG-2ByECiMe1x-2F3lW9R82ZhBfAujqs-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;" class="">
</div>
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></body></html>