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
Reverse-mode backends like Zygote and Enzyme (?) are able to return pullback functions / closures instead of just the return value of the pullback, which is currently returned by value_and_pullback!.
DI could offer a common interface value_and_pullback_fn (or a mutating value_and_pullback!_fn) for users in need of such closures.
The text was updated successfully, but these errors were encountered:
At first I thought we would be able to pull this off with the prepare mechanism, but now I see that prepare is specific for different inputs, whereas we reuse a pullback for the same input. So you have my go ahead ^^
Reverse-mode backends like Zygote and Enzyme (?) are able to return pullback functions / closures instead of just the return value of the pullback, which is currently returned by
value_and_pullback!
.DI could offer a common interface
value_and_pullback_fn
(or a mutatingvalue_and_pullback!_fn
) for users in need of such closures.The text was updated successfully, but these errors were encountered: