Automated type checking with Beartype #819
Merged
Conversation
This file contains 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
added 7 commits
August 9, 2021 17:57
|
❌ Deploy Preview for graspologic failed. 🔨 Explore the source changes: 34ca3ef 🔍 Inspect the deploy log: https://app.netlify.com/sites/graspologic/deploys/61130b576775f200081eb5ae |
nicaurvi
approved these changes
Aug 11, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reference Issues/PRs
none
What does this implement/fix? Briefly explain your changes.
This PR adds beartype runtime type checking to the "pipeline" package. Beartype checks input values against PEP-compliant type hints. When the type is nested (such as arrays or arrays of arrays) beartype samples data to maintain runtime speed.
Any other comments?