-
Notifications
You must be signed in to change notification settings - Fork 8
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
Add rem2pi #19
Add rem2pi #19
Conversation
I think we can fix this by just adding Instead of this PR, could you open a similar PR in https://github.com/JuliaDiff/DiffRules.jl instead? Sorry for the inconvenience - my plan is to archive DiffBase and RealInterface after JuliaDiff/ForwardDiff.jl#262 is merged. |
Transplanted from JuliaAttic/DiffBase.jl#19.
Transplanted from JuliaAttic/DiffBase.jl#19.
Adding
|
Thanks for looking into this. Simplest solution then might be to add the strictest supertype necessary to resolve the ambiguity (for this case, |
Fixes #18.
Unlike
rem
, I don't think it makes sense to addrem2pi
toRealInterface.BINARY_MATH
, because e.g. https://github.com/JuliaDiff/ForwardDiff.jl/blob/18b46471e4bb3d36633058267606767246b3e931/src/dual.jl#L420 won't do the right thing for this case. Same thing for the standard tests in RulesTests.jl.Please advise on how to handle this: should there be a new category in RealInterface containing only this function, or should this just be special cased directly in ForwardDiff and other RealInterface dependents?