It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat (don't just cc him here, he won't see it! He's on Discord!).

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

Please don't mark your own PRs as test-exempt, the whole point of the process is that every PR that doesn't have tests needs to be manually checked so as to denormalize the behaviour of writing PRs without tests.

Please don't mark your own PRs as test-exempt, the whole point of the process is that every PR that doesn't have tests needs to be manually checked so as to denormalize the behaviour of writing PRs without tests.

@Hixie everything that is landed is reviewed, so it is manually checked. In the case of writing tests it seemed we could trust the author and the reviewer to make that decision and that your attention was only required in more nuanced situations. In any case, I don't think there is harm communicating the explanation. Let me know if you want to format it differently.

I think for this case we should teach the bot about tests under the dev/benchmarks folder....

test-exempt: is a test