Extending Collector to handle a post-transform

Doug Lea dl at cs.oswego.edu
Wed May 29 08:11:51 PDT 2013

On 05/29/13 09:57, Tim Peierls wrote:
> On Tue, May 28, 2013 at 5:59 PM, Brian Goetz <brian.goetz at oracle.com
> <mailto:brian.goetz at oracle.com>> wrote:
>     Overall I think this is a reasonable price to pay for making the abstraction
>     more powerful.
> For me, this tips over into unacceptable territory. It's a lot of API complexity
> that most of the time wouldn't be used,

This is the multiple-audience problem that we grapple with all the time.
Most application-level stuff will never explicitly use a Collector at all.
So the main audience is people building layered stuff. And those are
likely to be the people most frustrated that they cannot do stuff
available in other similar languages/frameworks. Especially considering
that we are well aware of the limitations of not allowing cascading
transforms, it seems like a bad idea not to do this.


More information about the lambda-libs-spec-observers mailing list