[
https://issues.apache.org/jira/browse/JENA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596501#comment-14596501
]
A. Soroka edited comment on JENA-966 at 6/22/15 7:30 PM:
---------------------------------------------------------
I'd rather remove {{LazyIterator}} and add {{andThen(Supplier<Iterator<T>>)}}.
It seems to me to be a better pattern. Methods that accept {{T}} have a natural
match in "lazy" methods that accept a {{Supplier<T>}}, and this doesn't lead to
multiplying "lazy" types.
was (Author: ajs6f):
I'm suggesting that I'd rather remove {{LazyIterator}} and add
{{andThen(Supplier<Iterator<T>>)}}. It seems to me to be a better pattern.
Methods that accept {{T}} have a natural match in "lazy" methods that accept a
{{Supplier<T>}}, and this doesn't lead to multiplying "lazy" types.
> LazyIterator
> ------------
>
> Key: JENA-966
> URL: https://issues.apache.org/jira/browse/JENA-966
> Project: Apache Jena
> Issue Type: Bug
> Components: Core
> Affects Versions: Jena 3.0.0
> Reporter: Claude Warren
> Assignee: Claude Warren
>
> LazyIterator is an abstract class. The documentation indicates that the
> create() method needs to be overridden to create an instance. From this I
> would expect that
> now LazyIterator(){
> @Override
> public ExtendedIterator<Model> create() {
> ...
> }};
> Would work however LazyIterator does not override:
> remoteNext(), andThen(), toList(), and toSet().
> I believe these should be implemented in the class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
