Adrien Grand created LUCENE-7601:
------------------------------------

             Summary: Make DocIdMerger.next() unspecified when exhausted
                 Key: LUCENE-7601
                 URL: https://issues.apache.org/jira/browse/LUCENE-7601
             Project: Lucene - Core
          Issue Type: Task
            Reporter: Adrien Grand
            Priority: Minor


Right now there is a comment saying {{NOTE: it's annoying that caller is 
allowed to call us again even after we returned null before}}, but when I throw 
an exception in that condition, no tests fail. So maybe we can get rid of this 
protection now and just make next() unspecified after exhaustion, like 
{{DocIdSetIterator}}?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to