Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
dune-istl
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 26
    • Issues 26
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 22
    • Merge Requests 22
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Core Modules
  • dune-istl
  • Issues
  • #96

Closed
Open
Opened Oct 07, 2020 by Markus Blatt@markus.blattOwner

Policy/Assumptions on field_types in MultitypeBlockVector/Matrix?

I am trying to get rid of some warnings about shadowing variables/using directions. Some of them are due to using field_type = ... being reset in some methods (e.g. norms). I don't want to break anything, hence the question arises:

Do we insist on field_type being the same for each entry? Seems like the code at least insists that the field_types of all entries are convertible to the one of the very first entry.

For the template parameters, arbitrary different types are possible.

Our tests assume always use the same type.

Edited Oct 07, 2020 by Markus Blatt
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: core/dune-istl#96