Jon Pretty

@bitemyapp @puffnfresh val a = xs map (1 +) val b = a filter { _ < 10 } val c = a reduceOption { _ + _ } val d = c getOrElse 0 d #fail

@djspiewak @bitemyapp Warning: Defined but not used: `b'

@puffnfresh @bitemyapp :-) So, naming allows you to group and label chains of computation. Also makes it easier to refactor later.

@djspiewak @bitemyapp now try it without names, will you hit the "defined but not used" problem?

@puffnfresh @bitemyapp :-) My example was clearly facetious. I was pointing out how *not* to break things up by name.

@djspiewak @puffnfresh It just seems to flow more nicely. The intermediate steps often seem artificial, and forced.

@propensive @puffnfresh Right. I think my point though is that not all computations flow best with anonymous intermediate steps.

@djspiewak @propensive @puffnfresh also, you know, LOGGING!