:46 PM
Subject: Re: [functor] Use Validate.notNull and remove unreachable code
+1 to all FWIW
Matt
On Tue, Jul 24, 2012 at 4:28 AM, Simone Tripodi
simonetrip...@apache.org wrote:
Olá Bruno,
0) I would like to add the method Validate.notNull(...) where necessary in
[functor], if no one
] Use Validate.notNull and remove unreachable code
+1 to all FWIW
Matt
On Tue, Jul 24, 2012 at 4:28 AM, Simone Tripodi
simonetrip...@apache.org wrote:
Olá Bruno,
0) I would like to add the method Validate.notNull(...) where necessary in
[functor], if no one objects. Right now, I'm working
Olá Bruno,
0) I would like to add the method Validate.notNull(...) where necessary in
[functor], if no one objects. Right now, I'm working on the following
composite functors: TransformedProcedure, TransformedFunction,
TransformedBinaryProcedure and TransformedBinaryFunction. None of these
+1 to all FWIW
Matt
On Tue, Jul 24, 2012 at 4:28 AM, Simone Tripodi
simonetrip...@apache.org wrote:
Olá Bruno,
0) I would like to add the method Validate.notNull(...) where necessary in
[functor], if no one objects. Right now, I'm working on the following
composite functors:
Hi all,
I'm working on FUNCTOR-12 [1], writing tests for [functor] and learning more
about its code base, and could do with some help :-)
Some parts of [functor] code, specially constructors, use Validate.notNull(...)
from Commons Lang3. Other parts throw NullPointerException when the
