Skip to content

Add backward compatibility constructors for loop solver

This merge request tries to make feature/istl-ini !5 (closed) backward compatible for end users. This means:

  • Code of users or discretization modules using existing solvers and preconditioners shouldn't break.
  • I guess it is not easy to avoid that people who have written their own solvers or preconditioners have to adjust their code. But this seems to be an acceptable compromise.

As an example I wrote constructors for the LoopSolver class that should enable backward compatibility. I would be glad if someone could have a look at the code. I couldn't find a better solution and I want to avoid rewriting everything after adjusting all the constructors ;).

I don't want to spread information or discussion so please stick to !5 (closed) for general discussion of feature/istl-ini. If you have anything to say about this code or better approaches to solve this problem feel free to comment here.

Merge request reports