vyasr commented on issue #38325: URL: https://github.com/apache/arrow/issues/38325#issuecomment-2062811403
Hmm my interpretation of various comments above like this one: > Well, for me the question is: how do we later add options to the API without breaking compatibility with producers that don't implement those options? was that we wanted a way for consumers to be producer-agnostic up to and including allowing producers to silently ignore arguments that they do not support. How would we distinguish from whether an API was provided with a default value explicitly vs because that value is the default in the signature itself? To do that we would need to expose something like pandas NoDefault, which doesn't work here since we're defining a protocol without any centralized implementation where such a "no default" default object could live. -- 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]
