Skip to content

Commit 2829e2d

Browse files
committed
update md files
1 parent 6e9d48b commit 2829e2d

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

STYLE_GUIDE.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -20,9 +20,9 @@ This style guide is a living document and proposed changes may be adopted after
2020
* If the interface and implementation is split using submodules the implementation submodule file should have the same name as the
2121
interface (parent) module but end in `_implementation`
2222
E.g., `string_class.f90` and `string_class_implementation.f90`
23-
* Tests should be added in the `tests` subdirectory and have the same name as the module they are testing with the `test_` prefix
23+
* Tests should be added in the `test` subdirectory and have the same name as the module they are testing with the `test_` prefix
2424
added
25-
E.g., `string_class.f90` and `tests/test_string_class.f90`
25+
E.g., `string_class.f90` and `test/test_string_class.f90`
2626

2727
## Indentation & whitespace
2828

WORKFLOW.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -81,8 +81,8 @@ To add tests, the macro ``ADDTEST`` should be used instead of the CMake function
8181
``add_test``, the macro hides creation of the executable target, linking against the
8282
main library target and registering the test.
8383
The tests themselves are defined as standalone executables in the subdirectories
84-
in ``src/tests``, a new subdirectory with tests has to be registred in
85-
``src/tests/CMakeLists.txt``.
84+
in ``test``, a new subdirectory with tests has to be registered in
85+
``test/CMakeLists.txt``.
8686

8787
The source tree should be considered read-only. References to ``PROJECT_SOURCE_DIR``
8888
and ``CMAKE_CURRENT_SOURCE_DIR`` should only be used for accessing source files,

doc/specs/stdlib_hash_procedures.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -1623,7 +1623,7 @@ various hash functions. The other is a comparison of the outputs of
16231623
the Fortran hash functions, with the outputs of the C and C++ hash
16241624
procedures that are the inspiration for the Fortran hash functions.
16251625

1626-
In the `src/test/hash_functions_perf` subdirectory, the Fortran Standard
1626+
In the `test/hash_functions_perf` subdirectory, the Fortran Standard
16271627
Library provides two performance test codes for
16281628
the hash functions of `stdlib_hash_32bit` and
16291629
`stdlib_hash_64bit`, `test_32_bit_hash_performance` and
@@ -1726,7 +1726,7 @@ severely impact the performance of `nmhash32`, `nmhash32x`,
17261726
`water_hash`, `pengy_hash`, and `spooky_hash` relative to
17271727
`fnv_1_hash` and `fnv_1a_hash`.
17281728

1729-
In the `src/test/hash_functions` subdirectory, the Fortran
1729+
In the `test/hash_functions` subdirectory, the Fortran
17301730
Standard Library contains codes to test the validity of
17311731
the Fortran codes against the original C and C++ codes. It consists of one
17321732
executable `test_hash_functions` that

0 commit comments

Comments
 (0)