[
https://issues.apache.org/jira/browse/PIVOT-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13970550#comment-13970550
]
Sandro Martini commented on PIVOT-799:
--------------------------------------
Usually we put this kind of code in *Adapter classes, anyway for so-common
cases I think it's a good shortcut to have directly inside collection classes
:-) .
Just for Info: in Scala this kind of operations are done in companion classes,
like static object factories (
http://keramida.wordpress.com/2013/06/19/factory-objects-in-scala-code/ ,
http://daily-scala.blogspot.it/2009/09/companion-object.html ) ... maybe we
could implement something like this but in Java.
> extending Pivot collections
> ---------------------------
>
> Key: PIVOT-799
> URL: https://issues.apache.org/jira/browse/PIVOT-799
> Project: Pivot
> Issue Type: Improvement
> Components: core-collections
> Reporter: Sandro Martini
> Assignee: Sandro Martini
> Priority: Minor
> Fix For: 2.5, 2.1
>
> Attachments: Monad_sample_revised.groovy
>
>
> Add some usuful methods to Pivot Collections like those needed to process all
> elements, going more "function style", like addAll, contains, etc ...
> To simplify usage from people coming from other languages, try to align to
> other languages names/conventions (for what is possible) , like Scala, C# .
> Verify even if add a interface (defining a single method) that could be
> passed to some methods to contain logic for processing all elements (like the
> apply() in Scala), and chose a right name for it (maybe function or other
> similar).
> Some info here:
> http://apache-pivot-developers.417237.n3.nabble.com/Some-idea-on-extending-Pivot-collections-td3321472.html
> But for more changes in Collections (still to be discussed), wait the 3.0 ...
--
This message was sent by Atlassian JIRA
(v6.2#6252)
