-
Notifications
You must be signed in to change notification settings - Fork 28
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
Zygote compat is lacking #232
Comments
Hmm.... that's a good question.... I'm usually hesitant to add "*Core.jl" dependencies because a lot of them are of questionable usage but ChainRulesCore.jl might be an exception. One alternative solution is to make a glue package a la FastTransformsForwardDiff. (I'm wondering whether that should have been FastTransformsChainRulesCore.jl...) |
Either alternative is okay with me:) |
You just say which alternative you prefer, and I can try to contribute towards it. |
Let's put it in a separate package for now so we can work out the kinks. We can always merge it back here (in the event there's a good reason to have it). |
It seems this is a good use case for weak deps. Some packages already started moving ChainRules definition to weak deps. The definitions would be loaded only on Julia >= 1.9 (if you don't want to uae Requires on older Julia versions) but I think it would be the better long-term solution. |
It woul suck if we'd have to wait until Julia 1.9 before we could make use of this though 😕 |
I assume it already works with the beta version, so I think you can already use it without compiling julia. |
Can we do a separate package that works now, and becomes a weak dependency in Julia v1.9? |
If a weak dependency is loaded, an extension (usually a single file) in the |
I see. I think a weak dependency hear would be fine. I would suggest forgetting the separate project and just requiring v1.9 |
We use weak deps for ChangesOfVariables.jl now, and it works like a charm on Julia v1.9:
|
Zygote doesn't interact too nicely with LazyArrays.jl it seems, e.g.:
The first error can be "fixed" (I'm not entirely certain if this is the right way to go about it) by defining a chain rule:
Maybe the rest can be addressed this way too.
Are rules from CRC something that would be welcomed?
The text was updated successfully, but these errors were encountered: