[
https://issues.apache.org/jira/browse/UIMA-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15507883#comment-15507883
]
Marshall Schor commented on UIMA-5115:
--------------------------------------
I agree 1 is not desirable. At the very least, the fact that an "at(0,2)"
clause is included implies this is over Annotations, so that would be the
return type I would hope, of get.
But I think the way this happens is via (2), where it gets the type inferred
from the receiving variable.
Choice 3) seems not too useful - it adds a check but it seems it just forces
the user to write the type twice - once as the receiving argument, and once as
the extra argument to the select.
> uv3 select() api for iterators and streams over CAS contents
> ------------------------------------------------------------
>
> Key: UIMA-5115
> URL: https://issues.apache.org/jira/browse/UIMA-5115
> Project: UIMA
> Issue Type: New Feature
> Components: Core Java Framework
> Reporter: Marshall Schor
> Priority: Minor
> Fix For: 3.0.0SDKexp
>
>
> Design and implement a select() API based on uimaFIT's select, integrated
> well with Java 8 concepts. Initial discussions in UIMA-1524. Wiki with
> diagram: https://cwiki.apache.org/confluence/display/UIMA/UV3+Iterator+support
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
