Ian Bell

A) You need REFPROP 9.1.1 (email me at [email protected]) B) You should use the new cmake-based architecture: https://github.com/usnistgov/REFPROP-cmake

As it turns out, I have a fully working build system now in REFPROP-cmake. A bit of beta testing might not go amiss, but it builds and tests fine for...

@pettni : How about a docker container? That's ideally suited for this sort of problem of reproducibility. I have some experience there that I can share.

I think a new repo, perhaps ``autodiff/bench``, would make sense and then it can be pinned to particular versions of ``autodiff``, so you can do performance regression by bisection. @pettni...

Yes and no with binder. In theory you can provide a dockerfile, but it is better if you can install things with apt and friends. Here is a small example...

Right, I got that, but I could never get my constructed tuple to turn into a ``Wrt`` type. It seems possible, but I couldn't work it out.

This isn't exactly an issue in autodiff, but more a general one of C++, to convert my wrts tuple from the above to the Wrt type.

I think you might need to apply a horrible preprocessor macro trick to get this to work *right now*

Because ``wrt`` and ``Wrt`` are just pure-forwarding, and their arguments are not typed, and so therefore we can't use ``std::apply``

Yes, this is as I feared. For now, looks like macros are the only solution.