-
-
Notifications
You must be signed in to change notification settings - Fork 213
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
support ChainRules AbstractZero types #786
Conversation
Current state leaves three types of errors in tests:
and the deprecation warnings which will be gone once the Zygote adjoints are changed to use Zero() instead of nothing |
Co-authored-by: Lyndon White <oxinabox@ucc.asn.au>
This is interesting, I don't know what might have changed in the code that introduced a
This has causes problems before. |
be received
adjoint macro
Three issues remain: two similar errors [1], [2] coming from legacytype warning: difftype warning (needs to be turned on in [1]
[2]
|
I don't know the cause, I suspect it is something that Zygote was suposed to remove prior to that point. |
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.
Broadly looking good, just a few points to go over.
Are there some benchmarks to see the realized output bump in performance here? |
Let's wait til we have all the changes in. |
WIP for #603. Depends on this branch FluxML/ZygoteRules.jl#10
The work can be split into three parts:
This PR deals with the first part