IAP GITLAB
Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
corsika
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Issue analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Air Shower Physics
corsika
Commits
e7300f60
Commit
e7300f60
authored
6 years ago
by
Ralf Ulrich
Browse files
Options
Downloads
Patches
Plain Diff
Update GUIDELINES.md
parent
5432385e
No related branches found
No related tags found
1 merge request
!7
Resolve "Coding style"
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
GUIDELINES.md
+1
-3
1 addition, 3 deletions
GUIDELINES.md
with
1 addition
and
3 deletions
GUIDELINES.md
+
1
−
3
View file @
e7300f60
...
...
@@ -66,9 +66,7 @@ While `clang-format` does the structural formatting, we still need to agree on n
-
Code may not introduce any compiler errors, or warnings
-
All unit tests must succeed at all times
-
We use C++14 concepts wherever possible
-
Class members are initialized at definition
-
we use "= delete", "= default", etc. identifier in class functions
-
We use C++17 concepts wherever useful and helpful
-
On any major error or malfunction we throw an exception. This is needed and required for complex physics and shower debugging.
-
We never catch exceptions for error handling, there might be very few special exceptions from this. We need to discuss such cases.
-
Everything that should not change should be
`const`
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment