Updated State of the Lambda

[Howard Lovatt]

In my own parallel code a chain of retain/recycle events doesn't do
anything other than build the expression to be processed (builder pattern).
The action happens when you call either out or reduce. Therefore I would
not favour combining the methods since seperate methods read better and
combined methods offer no/little performance advantage.

On 13 December 2011 11:32, Stephen Colebourne <scolebourne at joda.org> wrote:

> On 12 December 2011 23:43, Dan Smith <daniel.smith at oracle.com> wrote:
> > Should we be criticizing this alternative as a Bad Thing?  I'm not sure
> there's a clear reason to do so.  I think the use of chaining in these toy
> examples is inspired by much bigger problems where there's a clear benefit
> to separating concerns.  (And in this particular case, the use of chaining
> evolved from a time when we were using a 'max' method.)
>
> But do we have metrics on the proportion of Java developers that have
> to deal with big data where this serious FP/parallel approach has real
> benefits? There is a danger of designing/documenting for the elite
> rather than the mainstream here, for whom imperative foreach loops and
> accumulators are not a huge problem right now.
>
> Stephen
>
>


-- 
  -- Howard.