Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

psys.com/software From: swift-evolution-boun...@swift.org [mailto:swift-evolution-boun...@swift.org] On Behalf Of Ben Rimmington via swift-evolution Sent: Thursday, April 20, 2017 12:12 PM To: Adrian Zubarev <adrian.zuba...@devandartist.com> Cc: swift-evolution <swift-evolution@swift.o

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

Yep I really did pitched this instead of a triple quoted multi-line literal string. let string = "Hello \ // Three trailing space characters "Swift\ " 4.0" // Three leading space characters print(string) // prints: "Hello___Swift___4.0" where _ is a space character

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

I’ve never thought about allowing hard wrapping from single quoted string literals until it come up during the latest discussion. At first glance I don’t have anything against it. I wouldn’t put comments into the mix for now, to keep things simple. (I’ve already asked about comments, but the

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

Two things: Shall we rename the thread for to focus onto the new topic? The toolchain is great, the multi-line string literal how I imagined it to be the whole time, except for two smaller issues. The the fix-it is wrong for the following two examples: """ 123 """ """ abc 123 """ It will ask

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

The main issue with that design is, even if it’s only bikeshedding here, that it creates ambiguity. let a = "Hello, " "world!" To me that reads like the string constant a would contain "Hello, " and the literal "world!" sits somewhere in the middle of your code and is unused. Nothing signals

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

Following this thread it reads to me that SE-0168 being accepted without newline escapes was regrettable as it gave us more flexibility in formatting “long strings”. As the core team rejected it on the basis that it was inconsistent with conventional string literals the obvious thing to do is

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

Hmm, I can see that Wux already replied to this question but let me give another more or less obvious answer which I believe has come up in a shape or another already: Brent Royal-Gordon via swift-evolution wrote: >> No, I am suggesting that whatever design is used

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

Sure, I can give an example. I'm not going to suggest that it'd win any awards, but: By restricting multiline literals to begin and end on distinct lines, the core team has established an interesting property. Namely, "literals" are delimited horizontally while """literals""" are delimited

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

> On Apr 22, 2017, at 8:12 AM, Xiaodi Wu wrote: > > On Sat, Apr 22, 2017 at 3:38 AM, Brent Royal-Gordon > wrote: >> On Apr 21, 2017, at 11:48 AM, Xiaodi Wu via swift-evolution >>

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

On Sat, Apr 22, 2017 at 3:58 PM, Thorsten Seitz wrote: > And just as `\n` is allowed in single-line string literals resulting in a >> multiline string it would make sense to allow `\` in multiline string >> literals to suppress literal newlines. >> The result would be >>

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

> Le 22 avr. 2017 à 22:58, Thorsten Seitz via swift-evolution > a écrit : > > You seem to be choosing to deliberately ignore what I (and others) write. Yes. I suggest people who want to hard wrap long strings literals to write a new proposal, on top of SE-0168

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

> Am 22.04.2017 um 21:27 schrieb Xiaodi Wu : > > On Sat, Apr 22, 2017 at 12:57 PM, Thorsten Seitz > wrote: > >> Am 22.04.2017 um 17:08 schrieb Xiaodi Wu > >: >> >> On

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

On Sat, Apr 22, 2017 at 12:57 PM, Thorsten Seitz wrote: > > Am 22.04.2017 um 17:08 schrieb Xiaodi Wu : > > On Sat, Apr 22, 2017 at 3:21 AM, Thorsten Seitz > wrote: > >> >> Am 21.04.2017 um 20:48 schrieb Xiaodi Wu via swift-evolution

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

> Am 22.04.2017 um 17:08 schrieb Xiaodi Wu : > > On Sat, Apr 22, 2017 at 3:21 AM, Thorsten Seitz > wrote: > >> Am 21.04.2017 um 20:48 schrieb Xiaodi Wu via swift-evolution >>

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

On Sat, Apr 22, 2017 at 10:42 AM, Xiaodi Wu wrote: > On Sat, Apr 22, 2017 at 10:35 AM, Robert Bennett > wrote: > >> I'm not sure how we could implement breaking lines with \ for single line >> strings. Either indentation has to be stripped from the

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

On Sat, Apr 22, 2017 at 10:35 AM, Robert Bennett wrote: > I'm not sure how we could implement breaking lines with \ for single line > strings. Either indentation has to be stripped from the broken line, or the > line must not be indented in which case nothing has been

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

I'm not sure how we could implement breaking lines with \ for single line strings. Either indentation has to be stripped from the broken line, or the line must not be indented in which case nothing has been gained because soft wrap would accomplish the same thing. (Is there an option I'm

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

On Sat, Apr 22, 2017 at 3:38 AM, Brent Royal-Gordon wrote: > On Apr 21, 2017, at 11:48 AM, Xiaodi Wu via swift-evolution < > swift-evolution@swift.org> wrote: > > This goes to my question to David Hart. Isn't this an argument for a > feature to allow breaking a

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

On Sat, Apr 22, 2017 at 3:21 AM, Thorsten Seitz wrote: > > Am 21.04.2017 um 20:48 schrieb Xiaodi Wu via swift-evolution < > swift-evolution@swift.org>: > > On Fri, Apr 21, 2017 at 1:45 PM, Erica Sadun wrote: > >> >> On Apr 21, 2017, at 12:40 PM, Xiaodi

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

> On 22 Apr 2017, at 10:21, Thorsten Seitz via swift-evolution > wrote: > > >> Am 21.04.2017 um 20:48 schrieb Xiaodi Wu via swift-evolution >> : >> >> On Fri, Apr 21, 2017 at 1:45 PM, Erica Sadun wrote: >>>

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

> On 22 Apr 2017, at 10:38, Brent Royal-Gordon via swift-evolution > wrote: > >> On Apr 21, 2017, at 11:48 AM, Xiaodi Wu via swift-evolution >> wrote: >> >> This goes to my question to David Hart. Isn't this an argument for a feature

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

> On Apr 21, 2017, at 11:48 AM, Xiaodi Wu via swift-evolution > wrote: > > This goes to my question to David Hart. Isn't this an argument for a feature > to allow breaking a single-line string literal across multiple lines? What > makes this a use case for some

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

> Am 21.04.2017 um 20:48 schrieb Xiaodi Wu via swift-evolution > : > > On Fri, Apr 21, 2017 at 1:45 PM, Erica Sadun > wrote: > >> On Apr 21, 2017, at 12:40 PM, Xiaodi Wu via swift-evolution >>

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

On Fri, Apr 21, 2017 at 2:42 PM, Robert Bennett wrote: > It looks like we have different interpretations about what "literal" means > (I think this may have been brought up in earlier messages in this thread; > I don't remember the resolution). I interpreted it as meaning

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

> On 21 Apr 2017, at 20:27, Ricardo Parada via swift-evolution > wrote: > > From Joe's email: > > "[...] > Discussion on the list raised the idea of allowing a line to end with \ to > "escape" the newline and elide it from the value of the literal; the core > team

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

It looks like we have different interpretations about what "literal" means (I think this may have been brought up in earlier messages in this thread; I don't remember the resolution). I interpreted it as meaning the same thing as literal in *LiteralConvertible, i.e., a Swift type that is

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

From Joe's email: "[...] Discussion on the list raised the idea of allowing a line to end with \ to "escape" the newline and elide it from the value of the literal; the core team had concerns about only allowing that inside multi-line literals and felt that that could also be considered later

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

t makes this >> a use case for some feature for _multiline_ string literals in particular? >> >> paragraphs are denoted by `\n` in almost every rich text tool / library >> >> >> _______ >> swift-evolution mailing lis

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

On Fri, Apr 21, 2017 at 1:46 PM, David Hart wrote: > > On 21 Apr 2017, at 20:20, Xiaodi Wu wrote: > > On Fri, Apr 21, 2017 at 8:45 AM, David Hart wrote: > >> >> On 21 Apr 2017, at 11:32, Adrian Zubarev via swift-evolution < >>

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

On Fri, Apr 21, 2017 at 1:45 PM, Erica Sadun wrote: > > On Apr 21, 2017, at 12:40 PM, Xiaodi Wu via swift-evolution < > swift-evolution@swift.org> wrote: > > On Fri, Apr 21, 2017 at 8:48 AM, Robert Bennett via swift-evolution < > swift-evolution@swift.org> wrote: > >>

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

> On 21 Apr 2017, at 20:20, Xiaodi Wu wrote: > >> On Fri, Apr 21, 2017 at 8:45 AM, David Hart wrote: >> >>> On 21 Apr 2017, at 11:32, Adrian Zubarev via swift-evolution >>> wrote: >>> >>> Dear Xiaodi Wu, why do you always

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

> On Apr 21, 2017, at 12:40 PM, Xiaodi Wu via swift-evolution > wrote: > > On Fri, Apr 21, 2017 at 8:48 AM, Robert Bennett via swift-evolution > > wrote: > Xiaodi, I think one thing you're neglecting is

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

On Fri, Apr 21, 2017 at 8:48 AM, Robert Bennett via swift-evolution < swift-evolution@swift.org> wrote: > Xiaodi, I think one thing you're neglecting is that users may never print > out a multiline literal string at all. A string might never be printed or > read by a human outside of the code it

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

On Fri, Apr 21, 2017 at 8:45 AM, David Hart wrote: > > On 21 Apr 2017, at 11:32, Adrian Zubarev via swift-evolution < > swift-evolution@swift.org> wrote: > > Dear Xiaodi Wu, why do you always have to be offensive in a way of > questioning every single word another person says

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

> Am 21.04.2017 um 15:45 schrieb David Hart via swift-evolution > : > > >> On 21 Apr 2017, at 11:32, Adrian Zubarev via swift-evolution >> wrote: >> >> Dear Xiaodi Wu, why do you always have to be offensive in a way of >> questioning

[swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

Xiaodi, I think one thing you're neglecting is that users may never print out a multiline literal string at all. A string might never be printed or read by a human outside of the code it resides in. In this case it seems perfectly reasonable to ask that it be possible to format the string

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

> On 21 Apr 2017, at 11:32, Adrian Zubarev via swift-evolution > wrote: > > Dear Xiaodi Wu, why do you always have to be offensive in a way of > questioning every single word another person says and not letting others to > have their own opinion?! I do not want to

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

Dear Xiaodi Wu, why do you always have to be offensive in a way of questioning every single word another person says and not letting others to have their own opinion?! I do not want to have a discussion with you that will and up you asking me why is the banana crooked. I expect a focused and a

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

On Thu, Apr 20, 2017 at 11:48 AM, Adrian Zubarev < adrian.zuba...@devandartist.com> wrote: > The multi-line string literal as it’s accepted right now only allows > pretty code generation with smaller lines. > This statement does not make sense to me. Multiline string literals allow (with the

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

> On 20 Apr 2017, at 17:48, Adrian Zubarev wrote: > > Some words about the trailing precision. Joe said that we could use \("") as > workaround, but if I recall correctly literals are banned from the > interpolation itself, which will result in us doing something like this: > > let end = "" >

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

Exactly, thank you for the clarification. That is the correct decision IMO. :) Here is the formatted version of the example from my last reply: https://gist.github.com/DevAndArtist/345ce0920de62349c1079e18201aea94 --  Adrian Zubarev Sent with Airmail Am 20. April 2017 um 18:58:07, Joe Groff

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

> On Apr 19, 2017, at 3:27 PM, Xiaodi Wu wrote: > > On Wed, Apr 19, 2017 at 5:24 PM, Joe Groff > wrote: > > > On Apr 19, 2017, at 3:16 PM, Xiaodi Wu via swift-evolution > >

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

The multi-line string literal as it’s accepted right now only allows pretty code generation with smaller lines. The literal itself is not reserved for JSON, XML and similar syntaxes only, which automatically implies the existence of conventions with longer lines. For whatever reasons a

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

You can use a plain text editor and no linter, or a plain text editor and a linter, or an IDE and no linter, etc., and in any of these scenarios you can already choose whether or not you want trailing newlines stripped. Why should the compiler try to enforce any rules here? Since Unicode is

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

True, but this is not about IDEs or editors. The feature itself doesn’t know what an editor is and what it capable of, nor should be ever rely on that. Not everyone uses the same settings and you cannot be 100% sure to expect the same string from looking at it, which was written in a different

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

On Wed, Apr 19, 2017 at 5:24 PM, Joe Groff wrote: > > > On Apr 19, 2017, at 3:16 PM, Xiaodi Wu via swift-evolution < > swift-evolution@swift.org> wrote: > > > > We had a very full debate about which way was superior during review; it > was proposed to behave one way and the

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

> On Apr 19, 2017, at 3:18 PM, Xiaodi Wu via swift-evolution > wrote: > > Other common tools like Git already flag trailing whitespace by default, so > even if Swift doesn't warn about it, you might still need to satisfy other > tools in your pipeline. > > Isn't

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

> On Apr 19, 2017, at 3:16 PM, Xiaodi Wu via swift-evolution > wrote: > > We had a very full debate about which way was superior during review; it was > proposed to behave one way and the core team decided on the other. We have to > let settled decisions be

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

On Wed, Apr 19, 2017 at 5:09 PM, Joe Groff wrote: > > On Apr 19, 2017, at 3:07 PM, Xiaodi Wu wrote: > > Hmm, I don't know that I agree. What's the harm of trailing spaces, and if > a warning, how would I silence it given that \ is rejected as a way to >

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

We had a very full debate about which way was superior during review; it was proposed to behave one way and the core team decided on the other. We have to let settled decisions be settled: that's the only way Swift Evolution will continue to work. On Wed, Apr 19, 2017 at 5:15 PM, Kevin Nattinger

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

I agree, but unfortunately it’s probably too late now. > On Apr 19, 2017, at 3:11 PM, Martin Waitz via swift-evolution > wrote: > > Hi, > > I think, it would be more natural to include the last newline. > Multi-line String literals are for multiple lines. > And each

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

Not to mention that many IDEs (at least have options to) trim trailing whitespace automatically, so it has a fair to high likelihood of breaking unexpectedly and invisibly. > On Apr 19, 2017, at 3:09 PM, Joe Groff via swift-evolution > wrote: > > >> On Apr 19,

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

Hi, I think, it would be more natural to include the last newline. Multi-line String literals are for multiple lines. And each line ends in a \n. Otherwise it wouldn’t be a line. Having """ line 1 """ + """ line 2 """ == """ line 1 line 2 """

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

> On Apr 19, 2017, at 3:07 PM, Xiaodi Wu wrote: > > Hmm, I don't know that I agree. What's the harm of trailing spaces, and if a > warning, how would I silence it given that \ is rejected as a way to suppress > a literal newline? \("") comes to mind, if nothing else.

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

Hmm, I don't know that I agree. What's the harm of trailing spaces, and if a warning, how would I silence it given that \ is rejected as a way to suppress a literal newline? On Wed, Apr 19, 2017 at 17:02 Joe Groff via swift-evolution < swift-evolution@swift.org> wrote: > On Apr 19, 2017, at

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

Not dealing with trailing whitespaces is indeed the right decision, I think. The idea has always been that one key advantage for this syntax is that one can copy and paste the greatest possible amount of multi-line text without having to edit each line. Many source documents can have such

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

> On Apr 19, 2017, at 2:43 PM, Adrian Zubarev > wrote: > > First of all, thank you for accepting the proposal. However I still have one > single concern left about the trailing whitespaces. Will the final > implemented version raise a warning or produce an

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

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 \n. """ Foo """ // Equals "\nFoo\n" --  Adrian Zubarev Sent with Airmail Am 19. April 2017 um 22:53:07, Vladimir.S via swift-evolution

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

First of all, thank you for accepting the proposal. However I still have one single concern left about the trailing whitespaces. Will the final implemented version raise a warning or produce an error when there are trailing whitespaces? The whole idea of a trailing \ was in first place to

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

> [...] a single newline is always stripped after the opening delimiter and > before the closing one. [...] Regards Anders > On 20 Apr 2017, at 04:52, Vladimir.S via swift-evolution > wrote: > >> On 19.04.2017 23:03, Joe Groff via swift-evolution wrote: >>

Re: [swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

On 19.04.2017 23:03, Joe Groff via swift-evolution wrote: Proposal Link: https://github.com/apple/swift-evolution/blob/master/proposals/0168-multi-line-string-literals.md Hello Swift Community, The review of SE-0168: "Multi-Line String Literals" ran from April 6...12, 2017. The proposal is

[swift-evolution] [Accepted] SE-0168: Multi-Line String Literals

Proposal Link: https://github.com/apple/swift-evolution/blob/master/proposals/0168-multi-line-string-literals.md Hello Swift Community, The review of SE-0168: "Multi-Line String Literals" ran