Github user ajs6f commented on a diff in the pull request: https://github.com/apache/jena/pull/90#discussion_r35807971 --- Diff: jena-base/src/main/java/org/apache/jena/atlas/iterator/Iter.java --- @@ -29,6 +29,14 @@ import org.apache.jena.atlas.lib.Closeable ; import org.apache.jena.atlas.lib.Sink ; +/** + * Iter provides utilities for working with {@link Iterator}s. + * + * Iter should never be used as a return type or parameter type in the public contract of a class. It is only to be used + * inside implementation code and is instantiated only to allow method-chaining as part of a calculation. --- End diff -- Yes, that's why the note is useful. If `Iter` actually imposed that in the code there would be no need for documentation. Is there in fact any difference between `Iter` and `ExtendedIterator`? They are both subtypes of `java.util.Iterator` that provide convenient methods, with the functionality of `Iter` entirely overlapping that of `ExtendedIterator`. I've tried repeatedly to discover this information, and my experience shows that it is quite possible to confuse them. You were quite explicit in explaining to me in connection with JENA-966 that they are not to be used in the same circumstances, and all I'm trying to do here is determine what those circumstances actually are and record them.
--- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---