News for hackers. Stuff that matters.
Re:Show HN: Pykov – a tiny Python module on finite regular M... by shoyer on Monday October 06, 2014 @08:26AM (#8415489)
True, but who really wants the mutating version? Worse, do we really want to make it more obvious/natural to modify in place? I think this is a standard library convention that is best forgotten. In pandas, for example, you need to write inplace=True to use the mutating versions of methods, which hopefully makes mutation awkward enough to discourage it.
Re:Show HN: Pykov – a tiny Python module on finite regular M... by andreasvc on Monday October 06, 2014 @08:35AM (#8415526)
More often than not, I want the in-place version. When dealing with a significant amount of data, it's better not to make unnecessary copies. What is your argument for wanting to discourage mutation? Either way, the argument of the parent comment is clear, it's best to follow established naming conventions.
Re:Show HN: Pykov – a tiny Python module on finite regular M... by shoyer on Monday October 06, 2014 @05:06PM (#8418311)
This stack overflow discussion summarizes pros of immutability reasonably well: http://stackoverflow.com/questions/1863515/pros-cons-of-immu...

The main reason is that mutable objects are more complex and thus harder to reason about (which leads to more bugs).