[raw-strings] Indentation problem
brian.goetz at oracle.com
Mon Feb 5 18:39:53 UTC 2018
> However, I also note that the broad problem may two or three distinct symptoms, and:
> (1) A solution that addresses one symptom may not address the others, and
> (2) On the other hand, it may (or may not) be perfectly reason to address the most painful symptoms in different ways, rather than insisting that a single solution cover them all.
Indeed so. This is one reason why we resisted the call to do string
interpolation (which many developers conflate with multi-line strings,
as many languages with one also have the other) at the same time.
Another way to ask this question is: are we yet sufficiently minimal?
We boiled it down quite a lot already, but are we at "minimal" yet? Or,
did we take a wrong turn in boiling it down, and find ourselves only a
> In particular, I happen to think that the problem of distinguishing snippet indentation from encoding-program indentation may require a rather different kind of solution from the problem of escape characters in embedded snippets. The reason is that in both these cases the painful symptom is visual in nature rather than logical. That’s why I can understand what drove Tagir to pursue the pipe-character approach (even though I think it may not be the best solution to the problem). We may want to use ```…``` to enclose regexes but also want to use some other approach to solve the multi-line / indentation problems.
OK, so what you're saying here is that it might be a clever
self-deception to count newline handling as "just another aspect of
More information about the amber-spec-observers