[
https://issues.apache.org/jira/browse/LUCENENET-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523746
]
Digy commented on LUCENENET-97:
-------------------------------
Jon,
Removing the IEnumerator interface(which is not used in anywhere) from
HitIterator and using the java names like next,hasNext etc. (with same logic)
can be an enough solution. With this change
1- User expectations from IEnumerator can be avoided.
2- Diversions from Lucene-java can be reduced.
DIGY
PS: "Implementing IEnumerator correctly" contradicts with the logic of Hits
class. It doesn't not return all the results at onces considering the
performance issues. The existance of HitIterator class(even in Lucene java) is
because of this.
> HitIterator does not correctly implement System.Collections.IEnumerator
> -----------------------------------------------------------------------
>
> Key: LUCENENET-97
> URL: https://issues.apache.org/jira/browse/LUCENENET-97
> Project: Lucene.Net
> Issue Type: Bug
> Environment: .NET
> Reporter: Neal Granroth
>
> method MoveNext() is supposed to increment the position within the list; it
> does not.
> method Current() is supposed to return the object at the current position,
> but not change the position within the list.
> It incorrectly moves to the next position.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
