[WIP, Proposal] Improve argument annotations interface #10746
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a container class with a bit of additional logic sprinkled on top in order to consistently handle argument annotations.
I propose argument annotations are parsed into an
ArgumentAnnotation
object as part of the input validation of all transformations (jit
,grad
, ...). These are then the objects that are passed around instead of tuples ofargnums
andargnames
. These tuples can be accessed when needed by lower level functions.This enables an easy and idiomatic way of ensuring arguments are validated while simultaneously providing an easy way to implement backwards compatibility through a subclass (not yet done).