-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test with vector as input #1059
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see how this tests the vector-conversion.
I propose to build a stdvector with standart data-types (int, double, ...), convert it to an sc_array and to compare its entries and other properties, such as length
Co-authored-by: David Knapp <[email protected]>
Co-authored-by: David Knapp <[email protected]>
Co-authored-by: David Knapp <[email protected]>
Co-authored-by: David Knapp <[email protected]>
This reverts commit d9d26d6.
Can you indent the files and take care for the failing tests please? |
… into test-with-vector-as-input
… into test-with-vector-as-input
… into test-with-vector-as-input
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the update! Please address my comments and also add your code to the CMake build system.
Co-authored-by: David Knapp <[email protected]>
Co-authored-by: David Knapp <[email protected]>
Describe your changes here:
Modified the existing t8_gtest_ghost_exchange file to take std::vector as input.
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.scp
to check the indentation of these files.Licence
doc/
(or already has one)