Immutability and Python
andrea crotti
andrea.crotti.0 at gmail.com
Mon Oct 29 11:44:31 EDT 2012
2012/10/29 Jean-Michel Pichavant <jeanmichel at sequans.com>:
>
> "return NumWrapper(self.number + 1) "
>
> still returns a(nother) mutable object.
>
> So what's the point of all this ?
>
> JM
>
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..
More information about the Python-list
mailing list