Hi Dom To support your proposal you provided an example. Well done for providing evidence to support your idea. Doing that makes the discussion more productive.
I'm going to use the words 'good' and 'bad', but with two provisos. The first is that they are judgemental, and often judgement is little more than personal opinion presented in an objective language. The second is that 'good' and 'bad' depend on context. The usual C-Python is not good at writing code where high performance is critical (but is fairly good at linking to external libraries that do provide high performance). However, often high-performance is of no importance when writing a prototype. For prototypes the forces are quite different than for production. With these provisos, a major purpose of a programming language is to make good code easier to write, and bad code harder to write. Hence the importance of you providing a coding example to support your idea. And also my request that you provide more information about the example code you kindly provided. Based on your example, I suspect that your proposed addition will make bad code easier to write. However, we don't need to discuss that now. I suggest that for your proposal to gain support an example of how it makes good code easier to write would be helpful. And also if you wish an example of how it makes bad code harder to write. Please note that my use of 'good' and 'bad' are subject to the provisos mentioned earlier. I hope this helps. Jonathan
_______________________________________________ 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/UOXPJVTGSF2FAUBALMHKCWYWNGT73QV4/ Code of Conduct: http://python.org/psf/codeofconduct/
