-
Notifications
You must be signed in to change notification settings - Fork 46
Improved Features types
#725
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
TobyBoyne
wants to merge
13
commits into
experimental-design:main
Choose a base branch
from
TobyBoyne:typing/feature-key-types
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from 4 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
7abff70
Better generic vars in features
TobyBoyne 4837e1c
Example of using typeguard
TobyBoyne 6113fc6
Move TypeGuard to top of function
TobyBoyne 0c9880f
`get` overloads and example for output
TobyBoyne 2460712
Add similar typing to Constraints
TobyBoyne b0ae8fd
Possible suggestion for using NewType with feature keys (see `torch_t…
TobyBoyne 4779c15
Merge branch 'main' into typing/feature-key-types
TobyBoyne 87ad757
Revert NewType change
TobyBoyne df132a7
Clean up get signatures in `Features` and `Inputs`
TobyBoyne c344d91
Switch from list to sequence for covariance
TobyBoyne a268633
Change calls on `Features`: down to 143 diagnostics
TobyBoyne 0fe4211
Clean up deterministic categorical and some constraints
TobyBoyne 0a06aa8
A bit more cleanup
TobyBoyne File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need the overload two times?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately that's part of the specification for overloads (link). I think the idea is that the actual implementation of
getshould have no type hints, and all of the type hints go into the different overloads.So the second overload is a fallback if the argument types don't match the first overload, which will happen if
excludesis provided, since you can't expressIntersection[GetIncludesT, ~GetExcludesT]in Python's type system (yet) so we need the fallback to be more generic!