timgrein commented on PR #16296: URL: https://github.com/apache/lucene/pull/16296#issuecomment-4810335494
> Did you encounter this in a real situation, or why the need to allow null? ( I'm just raising the question as I believe this api has been like this for a long time, and want to know if it's a real issue or just for consistency's sake ) @ChrisHegarty Yes I encountered it while working on a new CircuitBreaker for the inference API in Elasticsearch, where I've used it for RAM estimation. It felt inconvenient that I had to include a null-check, when I'm working with a single `Accountable` object vs. without a null-check when using an array. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
