What does this mean? That this won't work with better C at all?

How come future and not right in? This would allow: ``` string s = i""; ``` Yes?

Awesome!

There should be a bugzilla on this. There's zero reason for the compiler to lose this implicit conversion. Note that it works fine if the enum is done in some cases

What the struct/function does is essential to this DIP. While the implementation may change, the end result must be defined so code can reasonably know what to expect. To that end, I think the easiest thing is for the spec to say 3 things: 1. The struct will have an alias to the Parts. 2. The struct will define a `toFormatString` accessor, and define it's aspects 3. For the use case of calling C functions, the struct will alias this itself to a null terminated const char *, only when all format specifiers are provided. Then you can give a sample implementation.

How? Be explictly descriptive here. Example would have assist your case here.

Be more technical and less anecdotal here. What unintended errors would have occurred if this hypothetical string interpolation feature were to be implemented? How does it compare to your implementation?

This is too much anecdotal here. A comparison and description with python would be useful here.