(original) (raw)

On Fri, Dec 14, 2012 at 3:15 PM, Brian Goetz <brian.goetz@oracle.com> wrote:

So, the question remains -- is the word "mutable" (or some other way of saying that) a helpful guide about what is being done here, or pedantic noise that will irritate the users? �(Note that I think we should care much less how it makes people feel when \*writing\* code than how it helps comprehension when \*reading\* code.)

I don't think it's noise. It's going to be less common to come across "mutable" forms in practice, since they'll be harder to work with and�will�typically have to be wrapped in something more friendly. (That's my prediction, anyway.) So I think long descriptive names are fine here, like reduceThroughSideEffects or reduceHereBeDragons.

--tim