-
Notifications
You must be signed in to change notification settings - Fork 17
Enable testing of rules with @not_implemented
#140
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
Conversation
|
Hmm just thought, maybe one should use |
|
Nice, thanks for adding this here as well. I would support the use of With regards to the failing |
|
Thanks for adding the update. I think it is good to go, but I do have a suggestion for an improvement. If you are busy with other things I can open an issue we can tackle it separately. We use meta testing tools to test for errors:
Perhaps we could add a similar thing that would catch EDIT: probably best to tackle this separately |
Co-authored-by: Lyndon White <[email protected]>
oxinabox
left a comment
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.
Nice.
I have made some comments, but merge when you are happy.
Currently tests fail since
check_add!!errors forComposites with a field of typeNotImplemented: the implementation of+forCompositein ChainRulesCore useselementwise_addwhich is implemented with+but+is not defined forNotImplemented.My suggestion would be to allow operations with
Composites with fields of typeNotImplementedsimilar to howmuladdis enabled forNotImplemented, i.e.,NotImplementedwins always, but to not allow general calculations with+. This could be achieved by definingand using
_addinstead of+inelementwise_add. I already confirmed that this would fix the test errors.