On Fri, Jan 14, 2022 at 4:16 PM Andrew Beyer <beyer.andrew@gmail.com> wrote:
On Wed, Jan 12, 2022 at 2:52 PM Martin DeMello via Typing-sig
<typing-sig@python.org> wrote:
> I would suggest StringLiteral, since that's the common term, and further differentiates it from Literal[str] when read aloud.

Except it's a common term for a different thing. In my experience,
most languages seem to restrict the "string literal" terminology to
mean compile time values that exist in the source code (or at least
could be generated by a constant folding pass.)

 As I understand it, a 675String (not my naming suggestion! just a
placeholder :) also includes runtime values that can be assembled from
string literals by way of arbitrary runtime computation. I think
that's an important distinction, and one that would be muddled by
reusing an existing term that typically means something else.

That's a good point. Adding StaticString, ConstantString and SafeString to the mix then. I quite like SafeString because it conveys the intent of the designation, and the exact semantics can be spelt out more clearly in the documentation than in a name.

martin