[
https://issues.apache.org/jira/browse/PIVOT-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043195#comment-14043195
]
Sandro Martini commented on PIVOT-799:
--------------------------------------
Hi Roger, thanks, I wasn't aware because eclipse says nothing on those warnings
... I just committed some small changes.
Don't worry if all monad-related classes are a work-in-progress, in next weeks
I'm planning to make them work good (and add some unit test), and if possible
use even in some new methods in our colections.
Or if we find that they are not so useful for us, we can remove them later (but
they are in svn history at least) before the release.
Thanks for now. Bye
> 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,
> PIVOT-799_functions_and_options(initial).patch
>
>
> 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)
