gsmiller commented on PR #13559: URL: https://github.com/apache/lucene/pull/13559#issuecomment-2249072451
> Another idea -- would it help your use case? -- would be to support nextSetBit(start, end) . We could do this without adding any additional tracking in existing SparseBitSet methods. Basically instead of asking SBS to keep track, the client might be able to do so? ++ I like this suggestion as well but I wonder if the caller is always in a position to keep track of an `end`? It sounds like in your `TPBJQ` case though it's easy for the caller to know the range they're interested in, so maybe that's the right step here. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
