Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • dumux dumux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 91
    • Issues 91
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 80
    • Merge requests 80
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • dumux-repositories
  • dumuxdumux
  • Issues
  • #872
Closed
Open
Created Apr 22, 2020 by Timo Koch@timokOwner

Deprecation warnings from Dune::Hybrid::size

At some points, e.g. in the multidomain assembler, we use for Dune::MultiTypeBlockMatrix/Dune::MultiTypeBlockVector m:

using namespace Dune::Hybrid;
forEach(m, [](auto& row){
   ...
});

This accesses Dune::MultiTypeBlockMatrix::size which is deprecated since before dune 2.7 and causes the warning. Unfortunately this means we need to use a bit more verbose syntax:

using namespace Dune::Hybrid;
forEach(integralRange(M::N()), [](auto& i){
   auto& row = m[i];
   ...
});

should work.

A proposal to allow ::N() to de deduced from a range passed to Dune::Hybrid::forEach (https://gitlab.dune-project.org/core/dune-common/-/merge_requests/803) has been rejected for good reasons. The might be something like rows(m) in the future... but that doesn't help now.

Edited Apr 22, 2020 by Timo Koch
Assignee
Assign to
Time tracking