Github user ajs6f commented on a diff in the pull request:
https://github.com/apache/jena/pull/90#discussion_r35869523
--- 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 --
What I meant by "difference" was context of use. In other words, what I
have been trying to get at with this conversation, as I have written, is the
answer to "When should one use `Iter`, and when should one use
`ExtendedIterator`?" I tried to use `Iter` inside an `ExtendedIterator` during
JENA-966 and you explained that this was wrong, and I am trying to get Javadocs
into these classes so that other people don't have the same confusion.
I still have no idea when to use either. If the difference is purely
historical, then there is no inherent need for both, and perhaps I should open
a ticket for a slow, careful, un-disruptive migration towards a single type for
these purposes?
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
