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.

Regarding linking this PR to an issue, what kind of issue should I open? I didn't find anything that matches this kind of PR.

test-exempt: code refactor with no semantic change

@mateusfccp re the issue, you can just open a blank one (or follow any of the links above and ignore the template). It's just useful to have an issue in case the PR gets reverted (e.g. due to unrelated infra issues) so we don't forget to reland it.