Skip to content

Commit 0050f6f

Browse files
authored
Merge pull request #729 from goodmami/issue-728
Clarify that line-ending backslashes are unescaped
2 parents 164ebc9 + ce6ce00 commit 0050f6f

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

README.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -348,10 +348,11 @@ str3 = "Roses are red\r\nViolets are blue"
348348
```
349349

350350
For writing long strings without introducing extraneous whitespace, use a "line
351-
ending backslash". When the last non-whitespace character on a line is a `\`, it
352-
will be trimmed along with all whitespace (including newlines) up to the next
353-
non-whitespace character or closing delimiter. All of the escape sequences that
354-
are valid for basic strings are also valid for multi-line basic strings.
351+
ending backslash". When the last non-whitespace character on a line is an
352+
unescaped `\`, it will be trimmed along with all whitespace (including newlines)
353+
up to the next non-whitespace character or closing delimiter. All of the escape
354+
sequences that are valid for basic strings are also valid for multi-line basic
355+
strings.
355356

356357
```toml
357358
# The following strings are byte-for-byte equivalent:

0 commit comments

Comments
 (0)