[range-for] adapt remaining intersection loops in LocalResiduals
In the LocalResiduals, there are several protected functions taking an IntersectionIterator, void eval...(const IntersectionIterator &isIt, In order to be callable with an (address of an) intersection, the explicit requirement on the type IntersectionIterator has been relaxed: template<class InetrsectionIterator> void eval...(const IntersectionIterator &isIt, In a future steps these functions will be deprecated and replaced by equivalents that take intersection objects. Discussed with and approved by Christoph.
Showing
- dumux/freeflow/stokes/stokeslocalresidual.hh 7 additions, 9 deletionsdumux/freeflow/stokes/stokeslocalresidual.hh
- dumux/implicit/box/boxlocalresidual.hh 7 additions, 8 deletionsdumux/implicit/box/boxlocalresidual.hh
- dumux/implicit/cellcentered/cclocalresidual.hh 14 additions, 15 deletionsdumux/implicit/cellcentered/cclocalresidual.hh
- dumux/implicit/mpnc/mpnclocalresidual.hh 1 addition, 1 deletiondumux/implicit/mpnc/mpnclocalresidual.hh
- dumux/multidomain/couplinglocalresiduals/stokesnccouplinglocalresidual.hh 11 additions, 13 deletions...n/couplinglocalresiduals/stokesnccouplinglocalresidual.hh
- dumux/multidomain/couplinglocalresiduals/stokesncnicouplinglocalresidual.hh 11 additions, 13 deletions...couplinglocalresiduals/stokesncnicouplinglocalresidual.hh
Loading
Please register or sign in to comment