Since we have a tool to detect cycles now; and since we're entering
a phase where people can easily introduce cycles by accident (D100682)
or by request (D90999), I think it's increasingly important to shift
the burden of detecting these cycles onto the buildbot instead of
the poor human reviewer.
The buildkite output from a "cyclic dependency" failure looks like this: https://buildkite.com/llvm-project/libcxx-ci/builds/2610#485cdaa4-03e9-47af-9878-9b14d2647a1d
The buildkite output from a "non-ASCII in the headers" failure looks like this: https://buildkite.com/llvm-project/libcxx-ci/builds/2608#8ae5209d-9f5d-459c-ac7a-271e93ae70c7
Yikes, that's interesting! 'ascii' codec can't decode byte 0xe2 in position 392 means we're getting some sort of UTF-8 (e2 is a common onset in UTF-8) somewhere in one of the header files. But I don't see any such thing on my local laptop. I'll investigate by spamming buildkite. Please ignore the next few pokes. :) Once I diagnose that issue, I'll cause the intended build failure and link you to it.