<div dir="ltr">Hi Pavel, you&#39;ve misunderstood what I was saying. :)<div><br></div><div>I was focused specifically on the example Adrian posted a few messages up, where he cited wanting something like Python&#39;s implicit concatenation when a string is broken across multiple lines but each segment is still quoted; as Ricardo pointed out, that&#39;s not a significant improvement over adding + to the end of each line, and it&#39;s what I meant when I said doing the same things two ways.</div><div><br></div><div>I&#39;d be much more supportive of *true* multi-line strings or heredocs where the newlines that are part of the string in the source code are also part of the string—not just implicit concatenation around line breaks, but retaining the structure of the string as well. That&#39;s not two ways to do the same thing, since the latter isn&#39;t supported yet by Swift. So we&#39;re probably in agreement.</div><div><br></div><div>That being said, while I can see the necessity, I&#39;m actually not a fan of large strings in the middle of source code for many of the reasons cited already—I think it&#39;s a bit of a code smell to embed that much data in the source, and editors can have difficulty handling it when the syntax highlighting context changes to drastically. In my ideal world, I&#39;d like a way for me to import the contents of an external file as a String or a binary blob so that it still gets brought into the data segment but it&#39;s not a huge chunk of unrelated content in the middle of my logic.</div><div><br></div><div>That&#39;s a harder sell when you think of the Apple OS use cases because you can just load data from bundled resources, but it might be more valuable in server contexts, and if they could support interpolation as well, that would be a powerful templating mechanism as well.</div><div><div class="inbox-uyb8Gf" style="font-size:13px"><div><div class="inbox-msg6578138661800497928 inbox-F3hlO"><div class="gmail_msg" style="word-wrap:break-word"><div class="inbox-m_6578138661800497928bloop_markdown gmail_msg"><div><code class="inbox-m_6578138661800497928python gmail_msg"><br></code></div><p class="gmail_msg"></p></div><div class="inbox-m_6578138661800497928bloop_original_html gmail_msg"></div></div></div></div></div><div class="inbox-uyb8Gf" style="font-size:13px"></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Apr 3, 2017 at 11:44 AM Paweł Wojtkowiak &lt;<a href="mailto:neframair@gmail.com">neframair@gmail.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto" class="gmail_msg"><div class="gmail_msg">I think that there&#39;s nothing wrong with two &quot;tools&quot; for the same task in this case. Multiline strings look better in the code and are easier to read and can serve many purposes. By reading different texts from swift dev team I feel like this is something the language was designed with in mind. They&#39;re also easier to type and it needn&#39;t neccessarily be a string presented to the user. </div><div id="m_-3354027085141787946AppleMailSignature" class="gmail_msg"><br class="gmail_msg"></div><div id="m_-3354027085141787946AppleMailSignature" class="gmail_msg">Lets say I want a simple json literal for testing purposes - reading from a file takes much more effort comparing to inserting it directly in the code. Taking out every new line character makes it hard to read, and inserting quotes and pluses every line both needs extra effort and also decreases readability. Adding it as a multiline string would make a perfect solution for this to me.</div><div id="m_-3354027085141787946AppleMailSignature" class="gmail_msg"><br class="gmail_msg"></div><div id="m_-3354027085141787946AppleMailSignature" class="gmail_msg">There are so many other cases where this could be useful too. I like how python has the &quot;&quot;&quot; and I think this would be a good direction to go, although this is true that python uses indentation in a different way, so I think backslashes at the end of each line would be a nice idea - this is still better than concatenating each line with &quot; and +, and would have the least readability impact. Also, it could be treated as a literal and be evaluated at compile time.</div><div class="gmail_msg"><br class="gmail_msg"></div><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"></div></blockquote></div><div dir="auto" class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div dir="ltr" class="gmail_msg">I just checked with -O and without and was surprised to find that `let x = &quot;abc&quot; + &quot;def&quot; + &quot;ghi&quot;` wasn&#39;t collapsed into a single string literal &quot;abcdefghi&quot; in the generated assembly code. Maybe it&#39;s more difficult than it is in some other languages because of operator overloads and different kinds of text literals (strings, extended grapheme clusters, Unicode scalars)?<div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">Regardless of the reasons, a separate syntax isn&#39;t the right way to achieve this optimization—the compiler should just do it automatically. Like Ricardo, &quot;multi-line string literals&quot; should be reserved for string literals that include the newline characters that are used to break them up in source. The idea of supporting something like the Python example above just provides two ways to do the same thing, which I don&#39;t think we really need.</div><div class="gmail_msg"><br class="gmail_msg"></div></div><br class="gmail_msg"></div></blockquote></div><div dir="auto" class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div class="gmail_quote gmail_msg"><div dir="ltr" class="gmail_msg">On Mon, Apr 3, 2017 at 8:18 AM Ricardo Parada via swift-evolution &lt;<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a>&gt; wrote:<br class="gmail_msg"></div></div></div></blockquote></div><div dir="auto" class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"></div>I would think that the concatenation would get resolved at runtime, unless the compiler gets smart about it.  But either way I do not see it as a problem.  The reason is that I don&#39;t remember ever worrying about the performance of concatenating a few lines of text.  :-)<div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">Thanks</div></div></blockquote></div></div></blockquote></div><div dir="auto" class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg">On Apr 3, 2017, at 11:13 AM, Adrian Zubarev &lt;<a href="mailto:adrian.zubarev@devandartist.com" class="gmail_msg" target="_blank">adrian.zubarev@devandartist.com</a>&gt; wrote:</div><br class="m_-3354027085141787946m_4981237499957014445Apple-interchange-newline gmail_msg"></blockquote></div></div></div></div></blockquote></div></div></blockquote></div><div dir="auto" class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div class="m_-3354027085141787946m_4981237499957014445bloop_markdown gmail_msg" style="font-family:Helvetica,Arial;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(254,254,254)"><p style="margin:15px 0px" class="gmail_msg">To me a literal a single entity which is solved at compile time. The concatenation is however resolved at runtime if I’m not mistaken here (it might be optimized at compile time but I still would expect a function executed a couple of times at runtime).</p><p style="margin:15px 0px" class="gmail_msg">Please correct me if I’m wrong here.</p><div style="margin:15px 0px" class="gmail_msg"><br class="m_-3354027085141787946m_4981237499957014445webkit-block-placeholder gmail_msg"></div></div></div></blockquote></div></div></div></div></blockquote></div></div></blockquote></div><div dir="auto" class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div class="m_-3354027085141787946m_4981237499957014445bloop_original_html gmail_msg" style="font-family:Helvetica,Arial;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(254,254,254)"><div id="m_-3354027085141787946m_4981237499957014445bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;margin:0px" class="gmail_msg"><br class="gmail_msg"></div><br class="gmail_msg"><div id="m_-3354027085141787946m_4981237499957014445bloop_sign_1491232271296286208" class="m_-3354027085141787946m_4981237499957014445bloop_sign gmail_msg"><div style="font-family:helvetica,arial;font-size:13px" class="gmail_msg">-- <br class="gmail_msg">Adrian Zubarev<br class="gmail_msg">Sent with Airmail</div></div><br class="gmail_msg"><p class="m_-3354027085141787946m_4981237499957014445airmail_on gmail_msg" style="margin:15px 0px">Am 3. April 2017 um 17:10:36, Ricardo Parada (<a href="mailto:rparada@mac.com" style="color:rgb(65,131,196);background-color:inherit;text-decoration:none" class="gmail_msg" target="_blank">rparada@mac.com</a>) schrieb:</p></div></div></blockquote></div></div></div></div></blockquote></div></div></blockquote></div><div dir="auto" class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div class="m_-3354027085141787946m_4981237499957014445bloop_original_html gmail_msg" style="font-family:Helvetica,Arial;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(254,254,254)"><blockquote type="cite" class="m_-3354027085141787946m_4981237499957014445clean_bq gmail_msg" style="margin:15px 0px"><span style="margin-top:0px;margin-bottom:0px" class="gmail_msg"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg">How is that better than this?<div class="gmail_msg"><br class="gmail_msg"></div></div></div></span></blockquote></div></div></blockquote></div></div></div></div></blockquote></div></div></blockquote></div><div dir="auto" class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div class="m_-3354027085141787946m_4981237499957014445bloop_original_html gmail_msg" style="font-family:Helvetica,Arial;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(254,254,254)"><blockquote type="cite" class="m_-3354027085141787946m_4981237499957014445clean_bq gmail_msg" style="margin:15px 0px"><span style="margin-top:0px;margin-bottom:0px" class="gmail_msg"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="m_-3354027085141787946m_4981237499957014445bloop_markdown gmail_msg" style="font-family:Helvetica,Arial;font-size:13px;background-color:rgb(254,254,254)"><pre style="margin:15px 0px;font-family:Menlo,Consolas,&#39;Liberation Mono&#39;,Courier,monospace;font-size:10pt;border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;background-color:rgb(248,248,248);color:inherit;border:1px solid rgb(204,204,204);overflow:auto;padding:4px 8px;word-break:normal;word-wrap:normal" class="gmail_msg"><code class="m_-3354027085141787946m_4981237499957014445python gmail_msg" style="font-family:Menlo,Consolas,&#39;Liberation Mono&#39;,Courier,monospace;font-size:10pt;border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;background-color:rgb(248,248,248);color:inherit;border:0px;margin:0px;padding:0px;word-break:normal;word-wrap:normal">template = &quot;This is the first line.\n&quot; +
            &quot;This is the second line.\n&quot; +
            &quot;This is the third line.&quot;
</code></pre><div style="margin:15px 0px" class="gmail_msg"><br class="m_-3354027085141787946m_4981237499957014445webkit-block-placeholder gmail_msg"></div></div><div class="m_-3354027085141787946m_4981237499957014445bloop_original_html gmail_msg" style="font-family:Helvetica,Arial;font-size:13px;background-color:rgb(254,254,254)"></div></div></div></div></span></blockquote></div></div></blockquote></div></div></div></div></blockquote></div></div></blockquote></div><div dir="auto" class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div class="m_-3354027085141787946m_4981237499957014445bloop_original_html gmail_msg" style="font-family:Helvetica,Arial;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(254,254,254)"><blockquote type="cite" class="m_-3354027085141787946m_4981237499957014445clean_bq gmail_msg" style="margin:15px 0px"><span style="margin-top:0px;margin-bottom:0px" class="gmail_msg"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" style="margin:15px 0px" class="gmail_msg"><div style="margin-top:0px" class="gmail_msg">On Apr 3, 2017, at 10:42 AM, Ricardo Parada via swift-evolution &lt;<a href="mailto:swift-evolution@swift.org" style="color:rgb(65,131,196);background-color:inherit;text-decoration:none" class="gmail_msg" target="_blank">swift-evolution@swift.org</a>&gt; wrote:</div><br class="m_-3354027085141787946m_4981237499957014445Apple-interchange-newline gmail_msg"></blockquote></div></div></div></div></span></blockquote></div></div></blockquote></div></div></div></div></blockquote></div></div></blockquote></div><div dir="auto" class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div class="m_-3354027085141787946m_4981237499957014445bloop_original_html gmail_msg" style="font-family:Helvetica,Arial;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(254,254,254)"><blockquote type="cite" class="m_-3354027085141787946m_4981237499957014445clean_bq gmail_msg" style="margin:15px 0px"><span style="margin-top:0px;margin-bottom:0px" class="gmail_msg"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" style="margin:15px 0px" class="gmail_msg"><div style="margin-bottom:0px" class="gmail_msg"><div style="word-wrap:break-word" class="gmail_msg">It look prettier without the \n<div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">It&#39;s not laziness.</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">I want my code to look pretty.</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg"><br class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" style="margin:15px 0px" class="gmail_msg"><div style="margin-top:0px" class="gmail_msg">On Apr 3, 2017, at 10:40 AM, Adrian Zubarev &lt;<a href="mailto:adrian.zubarev@devandartist.com" style="color:rgb(65,131,196);background-color:inherit;text-decoration:none" class="gmail_msg" target="_blank">adrian.zubarev@devandartist.com</a>&gt; wrote:</div><br class="m_-3354027085141787946m_4981237499957014445Apple-interchange-newline gmail_msg"><div style="margin-bottom:0px" class="gmail_msg"><div class="m_-3354027085141787946m_4981237499957014445bloop_markdown gmail_msg" style="font-family:Helvetica,Arial;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(254,254,254)"><p style="margin:15px 0px" class="gmail_msg">What I was trying to say is that by automatically adding a new line character does not provide any benefit except of being lazy to type<span class="m_-3354027085141787946m_4981237499957014445Apple-converted-space gmail_msg"> </span><code style="font-family:Menlo,Consolas,&#39;Liberation Mono&#39;,Courier,monospace;font-size:10pt;border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;background-color:rgb(248,248,248);color:inherit;border:1px solid rgb(234,234,234);margin:0px 2px;padding:0px 5px;word-break:normal;word-wrap:normal" class="gmail_msg">\n</code>.</p><pre style="margin:15px 0px;font-family:Menlo,Consolas,&#39;Liberation Mono&#39;,Courier,monospace;font-size:10pt;border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;background-color:rgb(248,248,248);color:inherit;border:1px solid rgb(204,204,204);overflow:auto;padding:4px 8px;word-break:normal;word-wrap:normal" class="gmail_msg"><code class="m_-3354027085141787946m_4981237499957014445swift gmail_msg" style="font-family:Menlo,Consolas,&#39;Liberation Mono&#39;,Courier,monospace;font-size:10pt;border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;background-color:rgb(248,248,248);color:inherit;border:0px;margin:0px;padding:0px;word-break:normal;word-wrap:normal">// In your model this would be equivalent
let s1 = &quot;\n\n\n&quot;
let s2 = &quot;&quot;&quot;
    &quot; // However in my model this is an empty string and should be banned
    &quot;
    &quot;&quot;&quot; // That&#39;s also an empty string, but it that case it indicates the end of the multi lined string
</code></pre><p style="margin:15px 0px" class="gmail_msg">I dislike the tradeoff of precision for laziness.</p><div style="margin:15px 0px" class="gmail_msg"><br class="m_-3354027085141787946m_4981237499957014445webkit-block-placeholder gmail_msg"></div></div><div class="m_-3354027085141787946m_4981237499957014445bloop_original_html gmail_msg" style="font-family:Helvetica,Arial;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(254,254,254)"><div id="m_-3354027085141787946m_4981237499957014445bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;margin:0px" class="gmail_msg"><br class="gmail_msg"></div><br class="gmail_msg"><div id="m_-3354027085141787946m_4981237499957014445bloop_sign_1491230112191910912" class="m_-3354027085141787946m_4981237499957014445bloop_sign gmail_msg"><div style="font-family:helvetica,arial;font-size:13px" class="gmail_msg">-- <br class="gmail_msg">Adrian Zubarev<br class="gmail_msg">Sent with Airmail</div></div><br class="gmail_msg"><p class="m_-3354027085141787946m_4981237499957014445airmail_on gmail_msg" style="margin:15px 0px">Am 3. April 2017 um 16:29:44, Ricardo Parada (<a href="mailto:rparada@mac.com" style="color:rgb(65,131,196);background-color:inherit;text-decoration:none" class="gmail_msg" target="_blank">rparada@mac.com</a>) schrieb:</p><blockquote type="cite" class="m_-3354027085141787946m_4981237499957014445clean_bq gmail_msg" style="margin:15px 0px"><div style="margin-top:0px;margin-bottom:0px" class="gmail_msg"><div style="font-family:helvetica;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="gmail_msg"><span style="margin-top:0px;margin-bottom:0px" class="gmail_msg">By the way, the multi-line string should allow \n\n, or as many as you may want to throw in there.  I don&#39;t see a problem with that.</span></div><span style="margin-top:0px;margin-bottom:0px" class="gmail_msg"><br class="m_-3354027085141787946m_4981237499957014445Apple-interchange-newline gmail_msg"></span></div></blockquote></div><div class="m_-3354027085141787946m_4981237499957014445bloop_markdown gmail_msg" style="font-family:Helvetica,Arial;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(254,254,254)"><br class="m_-3354027085141787946m_4981237499957014445Apple-interchange-newline gmail_msg"></div></div></blockquote></div><br class="gmail_msg"></div></div></div></blockquote></div></div></div></div></span></blockquote></div></div></blockquote></div></div></div></div></blockquote></div></div></blockquote></div><div dir="auto" class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div class="m_-3354027085141787946m_4981237499957014445bloop_original_html gmail_msg" style="font-family:Helvetica,Arial;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(254,254,254)"><blockquote type="cite" class="m_-3354027085141787946m_4981237499957014445clean_bq gmail_msg" style="margin:15px 0px"><span style="margin-top:0px;margin-bottom:0px" class="gmail_msg"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" style="margin:15px 0px" class="gmail_msg"><div style="margin-bottom:0px" class="gmail_msg">_______________________________________________<br class="gmail_msg">swift-evolution mailing list<br class="gmail_msg"><a href="mailto:swift-evolution@swift.org" style="color:rgb(65,131,196);background-color:inherit;text-decoration:none" class="gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="gmail_msg"><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="gmail_msg"></div></blockquote></div></div></div></div></span></blockquote></div></div></blockquote></div></div></div></div></blockquote></div></div></blockquote></div><div dir="auto" class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">_______________________________________________<br class="gmail_msg">
swift-evolution mailing list<br class="gmail_msg">
<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="gmail_msg">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="gmail_msg">
</blockquote></div></div></blockquote></div></blockquote></div></div></div>