April 6, 2016
5:04 p.m.
On Wed, Apr 6, 2016 at 6:49 AM, Random832 <random832@fastmail.com> wrote:
Last time this came up, the conclusion was that making values views comparable was intractable due to the fact that they're unordered but the values themselves aren't hashable. Then the discussion got sidetracked into a discussion of whether the justification for not having them be hashable (Java does just fine with everything being hashable and content-based hashes for mutable objects) makes sense in a "consenting-adults" world.
At risk of repeating the derailment: while that's true, I'm also under the impression that interest in deeply immutable objects is growing in the Java community.