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
In the below example with a conditional, the types should be easily inferable. However, none of the types in the backwards pass are inferred. Why would this be?
Currently, this is expected; as part of the control flow handling, the pullbacks for a and b will get stored on a Vector{Any} stack, which will lose type information.
We're hoping that new compiler features will help with this in future, but for now it's not that high a priority.
Have there been any updates on this? I am using some hand-written special functions and the type-unstable code caused by this issue is very slow in comparison to ForwardDiff...
There has not. You could try #1195 to see if it performs any better for you, but generally the better ideas are to hide branching behind a function with a custom rule or to use branchless control flow like ifelse.
In the below example with a conditional, the types should be easily inferable. However, none of the types in the backwards pass are inferred. Why would this be?
Version info:
The text was updated successfully, but these errors were encountered: