Re: [ghc-steering-committee] Proposal #569: multiline string literals; Rec: accept

Yes that's true of course, but if we had a design that could cover raw strings as well, then we have one fewer quoting construct. I guess the real question is: do we need the ability to toggle between multiline and raw separately? That is, right now we have cooked single-line strings. This proposal is for cooked multiline strings, leaving raw strings for a separate proposal. But maybe we only need cooked single-line strings and raw multiline ones? That would be simpler. I think wisdom from other languages would be helpful here. I will post on the ticket. Richard

On Dec 31, 2023, at 12:04 PM, Eric Seidel wrote:

...

On Dec 29, 2023, at 07:19, Richard Eisenberg wrote:

On the other hand, I'm a little worried that this doesn't have support for raw strings. That is, even with this, there will still be some users who reach for quasiquotes for multi-line strings, if those strings contain backslashes.

I had a similar thought at first, but I think raw strings can be added independently of this proposal. So long as we are not closing the door to a future addition I think it is fine to take incremental steps.