Chris,

> I could change my implementation; I could use Jerzy's
> implementation...launch Mathematica...

But all of these could be implemented by introducing a different type
constructor called AD for each one. You could switch the
implementation of AD on the user and they wouldn't have to change a
line of their code. I've no doubt there's a real problem you're trying
to solve, but I'm trying to figure out what it is. Can you post an
example piece of code that would break if you exposed AD, and which
means you need to hide it? (I fully understand the idea of abstracting
over the algorithm, I'm just trying to pin down exactly why you need
the abstraction, and what breaks if you don't have it.)
--
Dan
_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe

Reply via email to