Yeah absolutely, those can be used in more ways than "wrapping"
another iterable and maybe another name would be appropriate, but your
transformer is just one special case for that. So whatever name we
pick there will be uses of it that wont fit well with the name.
I think it's nice to see you use
I just wanted to share something I just realized...
Today I've been looking at the Functors API in commons-collections to
see how that is applicable to the Traverser API in Neo. The one thing
I was missing in the Traverser API was Transformer. There are two
Predicate-like interfaces in the S
2 matches
Mail list logo
