Composing Programs – Python 3 in the tradition of SICP

Re:Composing Programs – Python 3 in the tradition of SICP by tome on Monday April 11, 2016 @03:35AM (#11470125)

> Note that just because something is mutable doesn't mean you have to mutate it

I agree, and I don't mutate it, but my third party libraries and my collegues functions will. Not all of them, but enough to introduce annoying bugs.

[ Parent | on HN ]

Re:Composing Programs – Python 3 in the tradition of SICP by devishard on Monday April 11, 2016 @10:10AM (#11471567)

This is why I asked, "Which library are you having a problem with?"

You've claimed that third party libraries and your colleague's functions will mutate the data structures you pass them, but this has very rarely been my experience.

[ Parent | on HN ]

Re:Composing Programs – Python 3 in the tradition of SICP by tome on Monday April 11, 2016 @03:52PM (#11474581)

You must have much better colleagues than me!

[EDIT: I shouldn't impugn my coworkers: I had trouble resisting the siren call of side effecting functions!]

[ Parent | on HN ]

Re:Composing Programs – Python 3 in the tradition of SICP by devishard on Tuesday April 12, 2016 @07:23PM (#11484471)

So don't do that!

[ Parent | on HN ]