You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A checker such as beartype would provide an extra layer of assurance that our type hints are actually correct. Runtime type checkers will be able to examine more complex type hints (such as jax array shapes as added in #746), which is an advantage over Pyright (#427). However, there currently doesn't seem to be any reason we can't have both! If performance is a concern, we can only run the runtime checker while running the test suite, but beartype is apparently fairly speedy so we could include it in the live package as well.
To check:beartype is already listed as a test dependency. Is this really a test dependency, or should it be moved to dev? Or change dependency to pytest-beartype?
The text was updated successfully, but these errors were encountered:
What's the issue?
A checker such as
beartype
would provide an extra layer of assurance that our type hints are actually correct. Runtime type checkers will be able to examine more complex type hints (such as jax array shapes as added in #746), which is an advantage over Pyright (#427). However, there currently doesn't seem to be any reason we can't have both! If performance is a concern, we can only run the runtime checker while running the test suite, butbeartype
is apparently fairly speedy so we could include it in the live package as well.To check:
beartype
is already listed as atest
dependency. Is this really a test dependency, or should it be moved todev
? Or change dependency topytest-beartype
?The text was updated successfully, but these errors were encountered: