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 40
    • Issues 40
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 14
    • Merge requests 14
  • 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
  • !139

Add walberla variant

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Stephan Seitz requested to merge seitz/walberla:add_walberla_variant into master Oct 11, 2018
  • Overview 6
  • Commits 4
  • Pipelines 0
  • Changes 7

Can we have std::variant/boost::variant in waLBerla? We can use boost::variant as a fallback until we move to C++ 17.

I was using std::variant for my discretization/boost::units module whenever I can either take a physical pressure in pascals or a physical density in kg/m^3 (will commit this maybe next week). std::visit could also be useful to write terse code that dynamically selects the right template at run time.

I didn't add a try_compile yet to CMakeLists.txt to decide whether to take std::variant or boost::variant.

Edited Oct 11, 2018 by Stephan Seitz
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: add_walberla_variant