1) If this feature existed in Python 3.11 exactly as described, would you use it? Definitely not. It significantly increases cognitive burden on the reader. If python didn't have pattern matching, walrus, ternary expressions, etc -- then maybe I would consider this as something harmless. But right now we are at risk of slowly turning a great language into a monstrosity. We already have a tool (an if statement) that solves this problem just as well, is a widely known pattern, and is a lot easier to read.
2) Independently: Is the syntactic distinction between "=" and "=>" a cognitive burden? Yes, but a slight one. 4) If "no" to question 1, is there some other spelling or other small change that WOULD mean you would use it? (Some examples in the PEP.) defer keyword that Andre proposed is a better option, in my opinion. However, I don't like the entire idea so I would argue against that as well. Don't take it as something bad -- it's a good idea in general but I believe that it's a step in the wrong direction specifically for python as it is. 5) Do you know how to compile CPython from source, and would you be willing to try this out? I do know how to compile it but I believe that the examples from your pep are great and paint a realistic enough picture of how it's going to feel so I'm afraid I have to refuse to test it. Sorry :) _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/5EAE2GP7SZ6M5MWKVFRQFIJ3PFUCZ6ML/ Code of Conduct: http://python.org/psf/codeofconduct/
