-
Notifications
You must be signed in to change notification settings - Fork 122
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
Impossible to provide custom pushforwards for functions that use functors #1023
Comments
gojakuch
added a commit
to gojakuch/clad
that referenced
this issue
Aug 13, 2024
Previously, if a user wanted to provide a custom pushforward for a function that uses functors in it, it was impossible to use a generated pushforwards for that functors' call operators. This commit aims to fix for basic functors that don't have multiple call operator overloads. Fixes: vgvassilev#1023
gojakuch
added a commit
to gojakuch/clad
that referenced
this issue
Aug 13, 2024
Previously, if a user wanted to provide a custom pushforward for a function that uses functors in it, it was impossible to use a generated pushforwards for that functors' call operators. This commit aims to fix for basic functors that don't have multiple call operator overloads. Fixes: vgvassilev#1023
gojakuch
added a commit
to gojakuch/clad
that referenced
this issue
Aug 13, 2024
Previously, if a user wanted to provide a custom pushforward for a function that uses functors in it, it was impossible to use generated pushforwards for that functors' call operators. This commit aims to fix this for basic functors that don't have multiple call operator overloads. Fixes: vgvassilev#1023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In this case, the compilation fails:
because at the time of parsing the custom derivative, the compiler doesn't know we're going to insert the
operator_call_pushforward
. we need to somehow bypass this in a user-friendly way, since this is a common pattern in modern frameworks like Kokkos.The text was updated successfully, but these errors were encountered: