-
Notifications
You must be signed in to change notification settings - Fork 3
Description
Moving this to a new issue from a discussion in #9 (comment)
which functions should have **kwargs in their signatures
I think we should follow the array API standard's lead https://data-apis.org/array-api/draft/purpose_and_scope.html#conformance:
A conforming implementation of the array API standard may provide additional features (e.g., values, objects, properties, data types, functions, and function arguments) beyond those described in this specification.
thus **kwargs does not appear in the standard.
I have mixed feelings on their stance. It makes for easier-to-read docs, but it's actually less correct from a static typing perspective. The Array API doesn't actually have statically typed reference code, only the docs, so our situation is a bit different.