Cleanup `schemes` and `operators`
- Currently we have three classes adding
schemes
method to operators (solve
and*Constraints
mostly). They all look the same so we should try to make that into one operator extension or wrapper - The a lot of code duplication in
dune.fem.operator
anddune.fem.scheme
which should be unified. We could for example always setup ascheme
is possible. Sodune.fem.scheme.galerkin
would forward todune.fem.operator
just checking that an ufl equation is used and the domain is equal to the range space.dune.fem.operator.foo
would then always add thescheme
extension/wrapper if the domain and range space are identical. So one would always getsolve
but I don't really see a disadvantage there. There might be other cases where solvers should/can not be added but I can't think of any.
Edited by Robert K