Strong types #1309
Open
Strong types #1309
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Davknapp
added
enhancement
Fun with the stl
src/t8_types/t8_operators.hxx
Outdated
Comment on lines
34
to
54
| /** | ||
| * \brief The CRTP pattern for operators. | ||
| * | ||
| * \tparam T | ||
| * \tparam crtpType | ||
| */ | ||
| template <typename T, template <typename> class crtpType> | ||
| struct crtp | ||
| { | ||
| T& | ||
| underlying () | ||
| { | ||
| return static_cast<T&> (*this); | ||
| } | ||
|
|
||
| T const& | ||
| underlying () const | ||
| { | ||
| return static_cast<T const&> (*this); | ||
| } | ||
| }; |
There was a problem hiding this comment.
Can we combine this with src/t8_schemes/t8_crtp.hxx?
There was a problem hiding this comment.
Thaught about it and had a short look into it. But this struct has an additional template argument than your implementation and I think that this is a detail that matters.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following our discussion in the C++-Meeting I started to implement strong types.
All these boxes must be checked by the reviewers before merging the pull request:
As a reviewer please read through all the code lines and make sure that the code is fully understood, bug free, well-documented and well-structured.
General
The reviewer executed the new code features at least once and checked the results manually
The code follows the t8code coding guidelines
New source/header files are properly added to the Makefiles
The code is well documented
All function declarations, structs/classes and their members have a proper doxygen documentation
All new algorithms and data structures are sufficiently optimal in terms of memory and runtime (If this should be merged, but there is still potential for optimization, create a new issue)
Tests
Github action
The code compiles without warning in debugging and release mode, with and without MPI (this should be executed automatically in a github action)
All tests pass (in various configurations, this should be executed automatically in a github action)
If the Pull request introduces code that is not covered by the github action (for example coupling with a new library):
Scripts and Wiki
script/find_all_source_files.scpto check the indentation of these files.License
doc/(or already has one)