Disable + and - rules on mixed numeric types #787
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is that constant tension in ChainRules between wanting to implement very general rules,
but not being sure you can rely on them to work for types that you can't trust to follow your epxectations.
This is the companion to JuliaDiff/Diffractor.jl#272
The version of this I have seen in the wild is calling Diffractor forwards mode over ForwardDiff,
and then getting
-(::Dual, Float64)
which is defined, but this can result in-(::Tangent{<:Dual}, Float64)
which is not defined.I am not convinced this is the best point to chose.
I think it might be argued that Diffractor's handling of
Dual
is aberant,and it should be constructing either a Tangent which is a
Dual
or it should be
@opt_out frule(::typeof(-), ::Dual, Float64)