I don’t think it’s a good idea to add optionally character before the closing delimiter, because it could confuse the reader of the code on how exactly the actual string lines above will be stripped.
My personal vision remains as the following example: // 1) """ Line_1 Line_2 """ // result for 1) "Line_1\nLine_2" // 2) """ Line_1 Line_2 """ // result for 2) "\nLine_1\nLine_2" // 3) """ Line_1 Line_2 """ // result for 3) "Line_1\nLine_2\n" // 4) """ Line_1 Line_2 """ // result for 4) "\nLine_1\nLine_2\n" This is the natural approach, alternatively you’re free to use directly \n instead a blank line. -- Adrian Zubarev Sent with Airmail Am 13. April 2017 um 19:47:18, David Sweeris ([email protected]) schrieb: On Apr 13, 2017, at 10:41, Adrian Zubarev <[email protected]> wrote: Was the / intended or did you meant to write \? Personally I don’t think we’d need that behavior and can fallback to the natural way using a blank lines or explicit way using the \n character to solve that issue at the top or bottom of the multi-line string. The model I’m pushing already would support “paste-in block of text as-is”. :) Hah, oops, yeah. Although maybe the "/" would be better for the closing """, since that one affects whether the preceding "\n" character is escaped. - Dave Sweeris
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
