On 2/20/19 7:46 PM, Christopher Barker wrote: > mutating operations vs copying operations > > functions vs methods. > > This has a lot of impact on the design, and it's very important that > any final syntax makes these distinctions clear.
Absolutely. > On Wed, Feb 20, 2019 at 8:33 AM Dan Sommers > <2qdxy4rzwzuui...@potatochowder.com> wrote: > > It's a different way of doing things. Please don't conflate them. > > however, that's kind of what this thread is all about :-) And I'm objecting to it. :-) > So is the goal here to get "fluent" syntax for stringing mutating > operations together that mutate the object? Not my goal, no. > ... we should extend the mutable sequence > ABC with methods that return new objects: > > list.sorted() > list.appended() > list.extended() Call me +0, or maybe +0.5 if adding such additional methods prevent adding new syntax. Dan _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
