[
https://issues.apache.org/jira/browse/UIMA-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15474778#comment-15474778
]
Marshall Schor commented on UIMA-1524:
--------------------------------------
I like the uniformity of these methods, and the fact that some of them have
lazy semantics (they don't compute things ahead of time, or copy things into
other instantiated arrays / lists).
V3 prereqs Java 8, which has a new kind of iterator, the SplitIterator.
Besides supporting parallism and streams, even if you don't take advantage of
that, it still provides a better (more efficient) iterator base than the
standard one.
So, I'd like to take the ideas from this part of uimaFIT and have similar ones,
but based around split iterators rather than Collections (unless we learn that
Collections provides additional usefulness that's worth the extra cost).
I also note that the many methods that do subiterator-like processing exclude
TypePriorities. I'm thinking that the choice to use / not-use TypePriorities
should be some kind of selectable thing, hopefully not polluting the API very
much. Suggestions appreciated!
> JFSIndexRepository should be enhanced with new generic methods
> --------------------------------------------------------------
>
> Key: UIMA-1524
> URL: https://issues.apache.org/jira/browse/UIMA-1524
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Affects Versions: 2.3
> Reporter: Joern Kottmann
>
> Existing methods should be overloaded with an additional Class argument to
> specify the exact return type. This changes make down casting of returned
> objects unnecessary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
