Ivan Levkivskyi

> That said, I still find the context parameter ugly. Probably off-topic for this issue, but there is one important argument why `context` may be needed even if we don't...

> But then we again have to answer the question what data structure is passed into signature, and how much about the pattern it reveals. I think as less as...

> Honestly I think the design of Gid() is wrong. This is just an example. Do you think having overloaded constructors is wrong in general? > Or else we should...

> But indeed, I'm happy to agree to disagree. Let me try to clarify where exactly we disagree. IIUC we agree that majority of people who will use pattern matching...

A real-life example is `Column` form `sqlalchemy`, it is either `Column(String)` or `Column("name", String)`. Also it is traditionally called by position, I have never seen `Column(type_=String)`. Various `sqlalchemy` related functions...

Yeah, just opened an issue for completeness. We can probably close this. How do you track ideas on which there is an agreement? Also, are we going to include all...

> I wonder if we could start with yours and just make edits to reflect our eventual positions. I can prepare some kind of a merged draft by updating the...

I agree. Note btw that a named sub-pattern (using walrus) is essentially an `&` between a name pattern and other pattern (as Guido suggested in OP). And this is IMO...

There is one downside to giving `continue` and `break` in match statement special meaning: there is a common code pattern where one loops over some values and has an `if...

I considered allowing `$(...)` with arbitrary expression (nor just `$name`) to load something a while ago. But after all I think it may be not a great idea. Some arguments:...