Chain filterArguments, or use identity()?

[Rémi Forax]

On 02/06/2011 07:40 PM, Attila Szegedi wrote:
> Hi folks,
>
> suppose I want to filter several disjunct ranges of arguments on a method handle. I noticed that filterArguments() no longer tolerates null elements in the filter array. This leaves me with two implementation strategies:
>
> 1. several chained filterArguments invocations, each specifying a continuous range of filters, or
> 2. replacing null elements in the filter array with appropriate MethodHandle.identity() elements.
>
> Which one is the advised approach (meaning, it will end up performing better)?
>
> Thanks,
>    Attila.

Hi Attila,
finally we decide to rollback that change, null are allowed in 
filterArguments().

one argument was that users will ask questions about performance of 
using identity()  :)

Rémi