Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • W waLBerla
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 41
    • Issues 41
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • waLBerla
  • waLBerla
  • Merge requests
  • !258

flattened shallow copy of field

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Michael Kuron requested to merge flatten into master Mar 06, 2020
  • Overview 0
  • Commits 5
  • Pipelines 8
  • Changes 12

As discussed on Mattermost with @bauer a few days ago, the memory layout of Field<Vector3<real_t>, 1> is the same as that of Field<real_t,3> and it is thus possible to use them interchangeably by converting the metadata appropriately.

One minor thing I don't like about my current implementation: things like VectorTrait<std::string> don't produce an error anymore. You can't use it because it doesn't have the setter and getter and its OutputType is void, but still it doesn't feel right. My attempts to conditionally disable Field::flattenedShallowCopy failed, so that changing VectorTrait was my workaround.

Edited Mar 11, 2020 by Michael Kuron
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: flatten