Hi all, for Pivot 2.1 we have some idea on extending Pivot collections, the related issue is here ( https://issues.apache.org/jira/browse/PIVOT-799 ), and we have some idea ...
To have better interoperability with Scala, and even because they have some powerful data-centric concepts, I'm thinking if could be useful even to implement in Pivot some of these concepts (like the Option pattern, etc ...), given all our constraints (stay in Java, etc) ... Maybe this could help us for a better adoption of Pivot in the Scala community ... some time ago I wrote in theis forums some question, but seems that none is interested, but things change with time, so maybe we could make another try :-) . Some link to interested code, just for info: http://www.scala-lang.org/api/current/index.html#scala.Option http://www.scala-lang.org/api/current/index.html#scala.Some http://www.scala-lang.org/api/current/index.html#scala.None$ http://www.scala-lang.org/api/current/index.html#scala.collection.Map I'm doing even a legal review with Apache Legals here ( https://issues.apache.org/jira/browse/LEGAL-142 ), to see how / what we can do, in case something will be implemented in Pivot ... Then (but not only for collection, so it's another story) maybe other things (but more on "concepts" than code), like "event sourcing", "reactive programming", "actors", etc ... What do you think ? Sandro
