[
https://issues.apache.org/jira/browse/JENA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14597501#comment-14597501
]
A. Soroka commented on JENA-966:
--------------------------------
I'm happy to leave this to y'all. I understand the desire to keep the interface
as narrow as possible, although I really do think that laziness is a natural
pairing.
On that minor point: I'm afraid you're wrong about the laziness of my design,
[@andy.seaborne]. If you look at the sample I give above, you will see that
every execution path containing {{Supplier::get}} goes through an {{Iterator}}
method. So it's fully lazy: {{Supplier:: get}} isn't called until an
{{Iterator}} method is called. {{Supllier}} is a very good way to induce
laziness. :)
> 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)
