<html><head><style>
body {
font-family: "Helvetica Neue", Helvetica, Arial, sans-serif;
padding:1em;
margin:auto;
background:#fefefe;
}
h1, h2, h3, h4, h5, h6 {
font-weight: bold;
}
h1 {
color: #000000;
font-size: 28pt;
}
h2 {
border-bottom: 1px solid #CCCCCC;
color: #000000;
font-size: 24px;
}
h3 {
font-size: 18px;
}
h4 {
font-size: 16px;
}
h5 {
font-size: 14px;
}
h6 {
color: #777777;
background-color: inherit;
font-size: 14px;
}
hr {
height: 0.2em;
border: 0;
color: #CCCCCC;
background-color: #CCCCCC;
display: inherit;
}
p, blockquote, ul, ol, dl, li, table, pre {
margin: 15px 0;
}
a, a:visited {
color: #4183C4;
background-color: inherit;
text-decoration: none;
}
#message {
border-radius: 6px;
border: 1px solid #ccc;
display:block;
width:100%;
height:60px;
margin:6px 0px;
}
button, #ws {
font-size: 12 pt;
padding: 4px 6px;
border-radius: 5px;
border: 1px solid #bbb;
background-color: #eee;
}
code, pre, #ws, #message {
font-family: Monaco;
font-size: 10pt;
border-radius: 3px;
background-color: #F8F8F8;
color: inherit;
}
code {
border: 1px solid #EAEAEA;
margin: 0 2px;
padding: 0 5px;
}
pre {
border: 1px solid #CCCCCC;
overflow: auto;
padding: 4px 8px;
}
pre > code {
border: 0;
margin: 0;
padding: 0;
}
#ws { background-color: #f8f8f8; }
.bloop_markdown table {
border-collapse: collapse;
font-family: Helvetica, arial, freesans, clean, sans-serif;
color: rgb(51, 51, 51);
font-size: 15px; line-height: 25px;
padding: 0; }
.bloop_markdown table tr {
border-top: 1px solid #cccccc;
background-color: white;
margin: 0;
padding: 0; }
.bloop_markdown table tr:nth-child(2n) {
background-color: #f8f8f8; }
.bloop_markdown table tr th {
font-weight: bold;
border: 1px solid #cccccc;
margin: 0;
padding: 6px 13px; }
.bloop_markdown table tr td {
border: 1px solid #cccccc;
margin: 0;
padding: 6px 13px; }
.bloop_markdown table tr th :first-child, table tr td :first-child {
margin-top: 0; }
.bloop_markdown table tr th :last-child, table tr td :last-child {
margin-bottom: 0; }
.bloop_markdown blockquote{
border-left: 4px solid #dddddd;
padding: 0 15px;
color: #777777; }
blockquote > :first-child {
margin-top: 0; }
blockquote > :last-child {
margin-bottom: 0; }
code, pre, #ws, #message {
word-break: normal;
word-wrap: normal;
}
hr {
display: inherit;
}
.bloop_markdown :first-child {
-webkit-margin-before: 0;
}
code, pre, #ws, #message {
font-family: Menlo, Consolas, Liberation Mono, Courier, monospace;
}
.send { color:#77bb77; }
.server { color:#7799bb; }
.error { color:#AA0000; }</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class="bloop_markdown"><p>This is the natural way of text blocks. If you really need a blank line you can add one at the start/end or alternatively use <code>\n</code>.</p>
<pre><code class="swift">"""
Foo
"""
// Equals "\nFoo\n"
</code></pre>
<p></p></div><div class="bloop_original_html"><style>body{font-family:Helvetica,Arial;font-size:13px}</style><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div> <br> <div id="bloop_sign_1492638545923299072" class="bloop_sign"><div style="font-family:helvetica,arial;font-size:13px">-- <br>Adrian Zubarev<br>Sent with Airmail</div></div> <br><p class="airmail_on">Am 19. April 2017 um 22:53:07, Vladimir.S via swift-evolution (<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>) schrieb:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>On 19.04.2017 23:03, Joe Groff via swift-evolution wrote:<br>> Proposal Link: <br>> https://github.com/apple/swift-evolution/blob/master/proposals/0168-multi-line-string-literals.md<br>> <br>> Hello Swift Community,<br>> <br>> The review of SE-0168: "Multi-Line String Literals" ran from April 6...12, 2017. The <br>> proposal is *accepted with revisions. *Community feedback was largely positive on the <br>> idea, though the discussion highlighted several under-specified aspects.<br>> <br>> - Questions arose about whether text could appear on the same line as the opening and <br>> closing delimiter, and how that would interact with the de-indentation algorithm. The <br>> core team feels that it is important to keep this feature focused on its purpose of <br>> allowing the easy embedding of pasted blocks of text, so *text inside the literal on <br>> the same line as either delimiter should be disallowed.*<br>> <br>> // Allowed, equal to "foo\nbar"<br>> """<br>> foo<br>> bar<br>> """<br><br>Could you clarify, shouldn't this be equal to "foo\nbar\n" ? I.e. with trailing \n <br>for "bar" line?<br>I didn't find any clarification about the injecting of line-end for last text <br>line(not for the """ delimiter).<br><br>> <br>> // Not allowed<br>> """foo<br>> bar<br>> """<br>> <br>> // Not allowed<br>> """<br>> foo<br>> bar"""<br>> <br>> This keeps the model straightforward to describe: a *single newline *is always <br>> stripped after the opening delimiter and before the closing one, and the closing <br>> delimiter's position always determines the indentation level of the entire literal. <br>> The core team acknowledges that single-line triple quoted strings have other uses in <br>> other languages, such as to avoid excessive escaping in a string that contains lots <br>> of literal quotes, but supporting that alongside the indentation-stripping behavior <br>> leads to a lot of subtlety, and there could be other solutions to the escaping <br>> problem down the line, such as raw strings. If nothing else, single-line triple <br>> quoted strings can be considered later as an additive feature.<br>> <br>> - The core team also believes that *underindentation or inconsistent tab/space usage <br>> within the indentation should be an error.* Every line inside the literal must begin <br>> with the exact sequence of spaces and tabs that precedes the closing delimiter.<br>> <br>> """<br>> <tab><space>this is OK<br>> <space><space>this is an error<br>> <space><tab>this is also an error<br>> <tab>under-indenting is an error too<br>> <tab><space><space>but you can go nuts after the indentation all you want<br>> <tab><space><tab>you do you<br>> <tab><space>"""<br>> <br>> - The quoted string should *normalize newlines* to \n in the value of the literal, <br>> regardless of whether the source file uses \n (Unix), \r\n (Windows), or \r (classic <br>> Mac) line endings. Likewise, when the compiler strips the initial and final newline <br>> from the literal value, it will strip one of any of the \n, \r\n, or \r line-ending <br>> sequences from both ends of the literal.<br>> <br>> // equal to "foo\nfoo\nfoo\nfoo"<br>> """^J<br>> foo^M^J<br>> foo^J<br>> foo^M<br>> foo^M<br>> """<br>> <br>> - It should be clarified that *multiline strings support the same escapes and <br>> interpolations* as single-line strings. This allows a literal """ to be written \""". <br>> Discussion on the list raised the idea of allowing a line to end with \ to "escape" <br>> the newline and elide it from the value of the literal; the core team had concerns <br>> about only allowing that inside multi-line literals and felt that that could also be <br>> considered later as an additive feature.<br>> <br>> Thanks John, Brent, and Tyler for the original proposal, and thanks to everyone who <br>> participated in the discussion!<br>> <br>> -Joe<br>> Review Manager<br>> <br>> <br>> _______________________________________________<br>> swift-evolution mailing list<br>> swift-evolution@swift.org<br>> https://lists.swift.org/mailman/listinfo/swift-evolution<br>> <br>_______________________________________________<br>swift-evolution mailing list<br>swift-evolution@swift.org<br>https://lists.swift.org/mailman/listinfo/swift-evolution<br></div></div></span></blockquote></div><div class="bloop_markdown"><p></p></div></body></html>