Open andrjohns opened 2 months ago
I think this makes sense to fix. Which signatures do you want to add/change? We would put this in 5.0 breaking changes
I think we want to keep the mix
implementation being called by default, since it's more efficient, but add a way to force the fwd
impl to be called.
I can think of two ways:
fwd
version to hessian_fwd
/hessian_fvar
/etchessian<false>(...)
resolves to the fwd
implThoughts/preferences?
Description
With the current signatures for
hessian
infwd
andmix
, it is not possible to call thefwd
implementation withdouble
types.mix/functor/hessian.hpp
:fwd/functor/hessian.hpp
:Because the scalar type is explicit in the
mix
signature and templated in thefwd
signature, calls tohessian
withdouble
types will always resolve to themix
implementation. This makes testing/validation (or even just use as an alternative) a bit of a hurdle.I think any kind of fix for this would imply a breaking change (changing function names/arguments), so could be bundled in the 5.0 release (@SteveBronder)?
Current Version:
v4.8.1