> On Apr 13, 2017, at 10:52, Adrian Zubarev <[email protected]>
> wrote:
>
> 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.
>
>
I think I'm inclined to agree... I'm just trying to think of ways to make those
who don't agree happy as well. Of course, as you pointed out, that necessarily
complicates things, which is itself something to consider.
Fortunately, we can add the syntax (or something else equally simple) to flip
the leading/trailing newline stripping behavior later, if it becomes necessary.
- Dave Sweeris
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
