Github user jpountz commented on the issue:
    > instead of directly returning the MatchesIterator
    I asked for this change so that you always get a fresh new iterator, even 
if you already iterated positions on the same field. I agree that making the 
call fully lazy would be ideal but I'm not too worried about it either given 
that this API is expected to be slow, eg. you can't use it to run queries.


To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to