On 2021-12-04 20:01, David Mertz, Ph.D. wrote:
There are perfectly good ways to "fake" either one if you only have the
other. Probably more work is needed to simulate early binding, but there
are ways to achieve the same effect.
However, that language would not be Python. That ship sailed in 1991.
What's being discussed here isn't changing the behavior of binding in
`def f(foo=bar)`.
Instead, it's a discussion of adding ADDITIONAL syntax for late-binding
behavior. I think the proposed syntax is the worst of all the options
discussed. But the real issue is that the cases where it is relevant are
vanishingly rate, and the extra cognitive, teaching, and maintenance
burden is significant.
This is a key point that I mentioned in another message (although that
message doesn't seem to have reaches the list for some reason).
Steven's list is very useful but I don't see any mention there of
languages that allow BOTH late-binding and early-binding, and
distinguishes them with some kind of syntactic flag in the signature.
--
Brendan Barnwell
"Do not follow where the path may lead. Go, instead, where there is no
path, and leave a trail."
--author unknown
_______________________________________________
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/WFCIHHCDJBMBX7J4SNHBNMXTHIP7SJ6D/
Code of Conduct: http://python.org/psf/codeofconduct/
