[swift-evolution] multi-line string literals

Travis Tilley ttilley at gmail.com
Mon Dec 14 14:54:05 CST 2015

I was going to wait a week to write up an actual official proposal and
submit a pull request to swift-evolution, but at 67 emails this has already
received a lot more feedback than most other topics already. It might not
be worth it to wait so long.

What I would really like to see is more use cases than my own and the
couple others we've seen in this thread. The SQL example showed me that the
indentation erasure rules might not be as simple as I assumed (which is a
good thing). The JSON example showed me that having unescaped syntax for
raw strings is also vital. Please keep the use cases coming, as my own
(docopt) really isn't all that complicated.

Chris Lattner has given a solid reason why extending normal strings to
multiple lines isn't the best of all potential options. I don't feel
strongly enough about the issue to argue one way or another and am inclined
to not change existing behavior.

Chris Lattner has also stated that he has no problem ripping out the
current compatibility logic for single quotes. What I'd really like to know
is if it would require multiple releases to properly handle changing their
behavior. If my currently limited understanding of Lexer.cpp is correct,
people are -already- being warned about using single quoted strings, so I
wouldn't feel bad about that behavior changing out from under them to
suddenly be unescaped.

I haven't delved much into the use cases for prefix/suffix extensions and
would like to hear more about this.

-Travis Tilley
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20151214/cceecb24/attachment.html>

More information about the swift-evolution mailing list