[Python-Dev] Re: PEP 642: Constraint Pattern Syntax for Structural Pattern Matching

2020年11月03日 01:52:48 -0800

Hello,
On Tue, 3 Nov 2020 10:30:22 +0100
Federico Salerno <[email protected]> wrote:
> Re: symbol for lookup
> 
> Whatever happened to the proposal of using . as prefix?
I guess, the same that happened with the proposals to use "+" as a
prefix, or proposals to change sides and use
"->" 
(https://mail.python.org/archives/list/[email protected]/thread/F22RLCDGKVMIBQKIJZAQYV3YCD45R2IQ/)
or ">" to mark variables to be bound.
> 
> If memory serves, the main objection was about it being hard to see,
> but is it really? We use fixed width fonts for a reason, and there
> are other places a dot is quite critical (has any php programmer ever
> mistaken a .= for a = ?) without it's size ever causing issues.
> 
> I think . is visible enough while being aesthetically inoffensive. Am
> i missing some problem or important past objection to it?
It's logically rather offensive. Dot is "structural sub-element"
operator. 
Given things like:
 from .foo import bar
 a.b = 1
something like:
 sth = "currently, I'm going to match by this value"
 match foo:
 case .sth:
 print("This looks really weird!")
looks really weird.
-- 
Best regards,
 Paul mailto:[email protected]
_______________________________________________
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/4NHQGHBMIOOTHPSC4H22K4UWNUCW34XN/
Code of Conduct: http://python.org/psf/codeofconduct/

Reply via email to