Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #32386
| References | <CAF_E5JZVij+DTNNH=kMHVa1+GM6g80MpQBY1N4wc-a46bmGLsw@mail.gmail.com> <771101937.3475467.1351525139677.JavaMail.root@sequans.com> <CAF_E5Jbf0KJjDLV0jS-p_J9E4D8=_sPScgE+vkmkN2sMw=3aoA@mail.gmail.com> |
|---|---|
| Date | 2012-10-29 15:48 +0000 |
| Subject | Re: Immutability and Python |
| From | andrea crotti <andrea.crotti.0@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.3021.1351525692.27098.python-list@python.org> (permalink) |
2012/10/29 andrea crotti <andrea.crotti.0@gmail.com>: >> > > Well sure but it doesn't modify the first object, just creates a new > one. There are in general good reasons to do that, for example I can > then compose things nicely: > > num.increment().increment() > > or I can parallelize operations safely not caring about the order of > operations. > > But while I do this all the time with more functional languages, I > don't tend to do exactly the same in Python, because I have the > impression that is not worth, but maybe I'm wrong.. By the way on this topic there is a great talk by the creator of Clojure: http://www.infoq.com/presentations/Value-Values
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Immutability and Python andrea crotti <andrea.crotti.0@gmail.com> - 2012-10-29 15:48 +0000
csiph-web