On Fri, 27 Nov 2020 08:56:18 -0500 Ned Batchelder <n...@nedbatchelder.com> wrote: > On 11/27/20 8:32 AM, Antoine Pitrou wrote: > > On Fri, 27 Nov 2020 07:32:17 -0500 > > 2qdxy4rzwzuui...@potatochowder.com > > wrote: > >> I come from old(er) school (1980s, 1990s) embedded systems, and who > >> "owns" a particular mutable data structure and how/where it gets mutated > >> always came up long before we wrote any code. No, I'm not claiming that > >> pre-ansi C and assembler are more productive or less runtime error prone > >> than newer languages, but is this feature only necessary because > >> "modern" software development no longer includes a design phase or > >> adequate documentation? > > "Modern" software development is just like older software development > > in that regard: sometimes it includes a design phase and/or adequate > > (i.e. sufficiently precise) documentation, sometimes it doesn't. > > > >> Memory management implementation details is a long way from executable > >> pseudo code. (30 years is a long time, too.) > > This isn't really about memory management, though. > > > Maybe it would help to clarify what it *is* about. The original > proposal makes no mention of the problem being solved.
Perhaps you could start by reading other messages posted by Serhiy and I in this thread, for example. I realize that trying to avoid redundant discussions is against the ethics and traditions of python-ideas, but still. Regards Antoine. _______________________________________________ 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/5B2V2G53BHQFCX2PHDMYUFGY55YBBZIW/ Code of Conduct: http://python.org/psf/codeofconduct/
