fluxo

This requires too much of an API change to implement in 3.0.3. Unassigning from 3.0.3, and we can revisit it in a later release. by ccurrens

We should probably look into doing this. There are several places in the code base where the dispose pattern is not used correctly in conjunction with iterators/enumerators. I am not...

How about something like... public abstract class TermEnum : IEnumerable, IDisposable { public abstract bool Next(); public abstract Term Term(); public abstract int DocFreq(); public abstract void Close(); public abstract...

The types I am aware of are the TermsEnum and DocIdSetIterator and their subclasses (which include DocsEnum and DocsAndPositionsEnum classes). There are probably a few others. Anything that is not...

Oh, one more thing. I was planning on getting to this after the next beta release. There are several bug fixes, optimizations, and 5 new NuGet packages I would like...

So I have a little time to get into this then Probably nothing new here to you. Mainly just me catching up... To your first point about GetEnumerator being somewhat...

No problem. I am just a bit surprised given the choice for some prime green field development vs this headache that you would choose this path. But nonetheless, my aching...

Yeah, well, I thought, that's looks like it might be isolated, small. Ha! I'll poke at it some more, see what turns up. But I may just punt and look...

Ahh...I think I now know where we are getting our wires crossed. You have become a victim of the Java developers' incessant need to abbreviate everything (which annoys the crap...

Yes, agreed. I think I wasn't quite using the right words to disambiguate. So... take a breath... lots of Esomething words coming.... Yes, the Enum types have the characteristics of...