[ https://issues.apache.org/jira/browse/PIVOT-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13972847#comment-13972847 ]
Sandro Martini commented on PIVOT-799: -------------------------------------- Hi, > But, along the lines of the companion classes, I was wondering if we could > create some generic factory methods that would automatically wrap things in a > ListAdapter or MapAdapter using generics. Not sure exactly what that would > look like, though. Is this kind of what you were thinking? yes, that was my main intent, but still I don't have a clear idea on how we could implement it (assuming it makes sense here) ... maybe later > 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)