Skip to content

Deprecate class HierarchicVectorWrapper and corresponding header

This was superseeded by istlVectorBackend(v). The difference between both is, that HierarchicVectorWrapper allows to specify the entry type used to terminate index resolution. In contrast istlVectorBackend() will always terminate for scalar entries. This seems to give the freedom to use vector-valued coefficients. However, we deliberately decided to only support scalar coefficients in dune-functions rendering this feature useless.

(Historically we supported vector-valued coefficients to ease the transition from the old bases in dune-fufem where this behavior was the only way to get vector-valued ansatz spaces.)

This MR also replaces the only usage of HierarchicVectorWrapper in the interpolate() wrapper for the python bindings by istlVectorBackend().

Side node: There is also a class Dune::Python::HierarchicVectorWrapper used in the python bindings for DiscreteGlobalBasisFunction. This class does not depend on the one in Dune::Functions::. I have no idea why this was added.

Merge request reports