Document string literals

[andrevidela]

#555, #1027, #1029 have been implemented, but the documentation and the changelog weren't updated at the same time. Documenting those feature is the last item in their todo list.

The features seem to work well except for #1755 and #1132 which are fairly innocuous.

[gallais]

I'm confused: why do you have \##n instead of \n?
According to the next example using a multiline string you do want the newline?

[andrevidela]

Yes I do want the newline. You need to use \##n Because the escape sequence is \## in that string, if you were to write \n the text \n would appear instead of a new line.

[gallais]

I see. I always understood \n as a single character, not as n being escaped to mean newline. 🤔

[andrevidela]

the character n preceeded with the escape sequence renders a single character, just like \t, \r, \0. Raw strings allow the user to type those character without having to escape the \ character. But you can recover their meaning by using the \# escape sequence inside a raw string (or however many # you're using for the raw string)