Discussion Thread: DIP 1036--String Interpolation Tuple Literals--Community Review Round 2

[Meta]

On Thursday, 4 February 2021 at 17:14:31 UTC, Adam D. Ruppe wrote:
> On Thursday, 4 February 2021 at 17:04:20 UTC, Meta wrote:
>> Your response confuses me a bit, so can you define "not 
>> actually do anything with it"? You'd do all the normal things 
>> you do with strings. Print them, parse them, replace 
>> sequences, etc.
>
> So you'd pass them to functions. Which, with a mature library 
> ecosystem, doesn't actually need anything beyond the naked 
> tuple! It would just work without any conversions.
>
> Heck, functions like `writeln` and `text` already just work in 
> the POC with no implicit conversions at all, no explicit 
> library overlaods. And you can use those to do the translation 
> anyway when you do need it.

I think it comes down to, when people (primarily and especially 
new users) see "", they expect a string. To get a weird (to them) 
tuple thing instead is just not a good user experience. Even if 
libraries can be made to work with "auto-tuple" strings, I really 
don't think we should be asking them to participate in this 
façade; it's an illusion that breaks on cursory inspection.

IMO it should be strings first, tuples if you ask.