1<!-- 2Please do not submit pull requests changing the `version.hpp` 3or the single-include `catch.hpp` file, these are changed 4only when a new release is made. 5 6Before submitting a PR you should probably read the contributor documentation 7at docs/contributing.md. It will tell you how to properly test your changes. 8--> 9 10 11## Description 12<!-- 13Describe the what and the why of your pull request. Remember that these two 14are usually a bit different. As an example, if you have made various changes 15to decrease the number of new strings allocated, thats what. The why probably 16was that you have a large set of tests and found that this speeds them up. 17--> 18 19## GitHub Issues 20<!-- 21If this PR was motivated by some existing issues, reference them here. 22 23If it is a simple bug-fix, please also add a line like 'Closes #123' 24to your commit message, so that it is automatically closed. 25If it is not, don't, as it might take several iterations for a feature 26to be done properly. If in doubt, leave it open and reference it in the 27PR itself, so that maintainers can decide. 28--> 29