Fixing clang tidy warnings for boundary module (4ce9e93b) · Commits · Frederik Hennig / waLBerla · GitLab

Skip to content

GitLab

Explore

Sign in

Primary navigation

Project

W

waLBerla
- Activity
- Members
- Labels
- Releases
- Package Registry
- Terraform modules
- Service Desk

Snippets Groups Projects

Admin message

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Frederik Hennig
waLBerla
Commits
4ce9e93b

Commit 4ce9e93b authored 3 months ago by

Philipp Suffa

Downloads
- Patches
- Plain Diff

Fixing clang tidy warnings for boundary module

parent d6c354df

Changes 9

Hide whitespace changes

Inline Side-by-side

Showing

src/boundary/Boundary.h 2 additions, 2 deletions

src/boundary/Boundary.h
src/boundary/BoundaryHandling.h 15 additions, 16 deletions

src/boundary/BoundaryHandling.h
src/boundary/BoundaryHandlingCollection.h 0 additions, 2 deletions

src/boundary/BoundaryHandlingCollection.h
src/lbm/boundary/ParserUBB.h 2 additions, 2 deletions

src/lbm/boundary/ParserUBB.h
src/lbm/boundary/SimpleDiffusionDirichlet.h 2 additions, 2 deletions

src/lbm/boundary/SimpleDiffusionDirichlet.h
src/lbm/boundary/UBB.h 2 additions, 2 deletions

src/lbm/boundary/UBB.h
src/lbm/boundary/factories/DefaultBoundaryHandling.h 2 additions, 2 deletions

src/lbm/boundary/factories/DefaultBoundaryHandling.h
src/lbm/boundary/factories/DefaultDiffusionBoundaryHandling.h 6 additions, 6 deletions

...lbm/boundary/factories/DefaultDiffusionBoundaryHandling.h
src/lbm/boundary/factories/ExtendedBoundaryHandlingFactory.h 3 additions, 3 deletions

src/lbm/boundary/factories/ExtendedBoundaryHandlingFactory.h

with 34 additions and 37 deletions

0% or .

You are about to add 0 people to the discussion. Proceed with caution.

Finish editing this message first!

Please register or sign in to comment