Jim Baker

Agreed. There are many available disambiguating characters available. I'm personally in favor of ^ as a prefix, which would cause no ambiguity. On Thu, Jul 2, 2020, 7:05 PM Daniel...

I believe the decision tree should be opaque when executed in the match statement, regardless of the action of any guards or "interesting" classes. The analogy I'm thinking of is...

@Tobias-Kohn The abstract semantics of the "black box" model is roughly 1. Upon entry to the match, everything is frozen with respect to any lookups (attributes, isinstance, hasattr, __match_args__, ...)....

Correct, and this is a good example of what can practically be folded.

Yes, I saw it was rejected, but I wanted to make sure we considered the above args before finally rejecting it :) I missed issue #2 's comments. It does...

Re: Space between tag and string literal? **No**, this is not possible with other prefixes. This also is a potential point of confusion where users may want to combine prefixes...

> Do we support all the special syntax allowed in f-string interpolations, i.e. `{x!r}`, `{x!s}`, `{x!a}`, `{x = }`? Yes. Note that for `some text {x=}`, this is rewritten at...

`formatspec` should be an empty string `''`, not `None`. This allows for direct usage of the `formatspec` with ``` format(getvalue(), formatspec) ``` as opposed to requiring ``` format(getvalue(), '' if...

@rmorshea So we have two choices for "tag string" per this insightful Wikipedia article on noun adjuncts, https://en.wikipedia.org/wiki/Noun_adjunct: * Use a noun adjunct construction. So this is "tag string" or...

The problem with `@` is that it already has a valid parse in Python. So let's write the following: ``` >>> class HTML: ... def __matmul__(self, other): ... print(f'Multiplying {self=}...