@@ -34,8 +34,8 @@ The `bin/test.sh` and `bin/bench.sh` are custom scripts to perform test
34and benchmarking tasks conveniently. They support running a group of
34and benchmarking tasks conveniently. They support running a group of
35tests or benchmarks, coverage, using correct optimization flags for
35tests or benchmarks, coverage, using correct optimization flags for
36benchmarking, benchmark comparison reports etc. Use the `--help` option
36benchmarking, benchmark comparison reports etc. Use the `--help` option
37−to see how to use these. See [benchmark/README.md](/benchmark/README.md)
37+to see how to use these. See [benchmark/README.md](/docs/Developer/Benchmarks.md)
38−and [test/README.md](/test/README.md) for more details.
38+and [test/README.md](/docs/Developer/Tests.md) for more details.
40You can also run tests or benchmarks directly for example:
40You can also run tests or benchmarks directly for example:
@@ -88,7 +88,7 @@ Here is a quick checklist for a PR, for details please see the next section:
88* Tests are added to cover the changed parts
88* Tests are added to cover the changed parts
89* All [tests](/test) pass
89* All [tests](/test) pass
90* [Performance benchmarks](/benchmark) are added, where applicable
90* [Performance benchmarks](/benchmark) are added, where applicable
91−* No significant regressions are reported by [performance benchmarks](/benchmark/README.md)
91+* No significant regressions are reported by [performance benchmarks](/docs/Developer/Benchmarks.md)
92* Haddock documentation is added to user visible APIs and data types
92* Haddock documentation is added to user visible APIs and data types
93* Tutorial module, [Introduction](/docs/Tutorials/Introduction.md), and [guides](/docs) are
93* Tutorial module, [Introduction](/docs/Tutorials/Introduction.md), and [guides](/docs) are
94 updated if necessary.
94 updated if necessary.
@@ -146,7 +146,7 @@ BRANCH.
147It is a good idea to include tests for the changes where applicable. See
147It is a good idea to include tests for the changes where applicable. See
148the existing tests in the [test](/test) directory. Also see the
148the existing tests in the [test](/test) directory. Also see the
149−[test/README.md](/test/README.md) for more details on how to run the tests.
149+[test/README.md](/docs/Developer/Tests.md) for more details on how to run the tests.
151### Documentation
151### Documentation
@@ -163,7 +163,7 @@ any of the existing performance benchmarks. If you introduced something new
163then you may want to add benchmarks to check if it performs as well as expected
163then you may want to add benchmarks to check if it performs as well as expected
164by the programmers to deem it usable.
164by the programmers to deem it usable.
166−See the [README](/benchmark/README.md) file in the `benchmark` directory for more
166+See the [README](/docs/Developer/Benchmarks.md) file in the `benchmark` directory for more
167details on how to run the benchmarks.
167details on how to run the benchmarks.
169The first level of check is the regression in "allocations", this is
169The first level of check is the regression in "allocations", this is