Hack up loopy's type system for our needs
When treating with return values from library calls we need to have knowledge of the type of the temporary we want to generate.
For this purpose we need to
-
implement Dune specific types -
register dune-specific types with the DuneTarget
-
hack up the interface of LoopyType
after discussion with Andreas to break the 1:1 mapping ofnumpy.dtpye
to type in target
I tried doing this before but I was confused about whether loopy makes a distinction between a type and an array axis implementation type.
Consider std::vector<Dune::FieldVector<double, dim> >
. While the underlying type double
is obviously represented by a LoopyType
I am not
sure about the rest...