jpountz commented on PR #14413:
URL: https://github.com/apache/lucene/pull/14413#issuecomment-2759377415

   @jainankitk OK. In my opinion, it's more important to handle the concurrent 
and non-concurrent cases consistently than to save some overhead when searches 
are not concurrent. I'd really like non-concurrent search to look and feel like 
a concurrent search with a single slice running on a SameThreadExecutorService 
as far as profiling is concerned. So I wouldn't specialize the class hierarchy 
for concurrent vs. non-concurrent.


-- 
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

Reply via email to