[cperciva]

Who would want to have 'fickle_timestamps' or 'fudged_routing'?

Not quite the same thing. What I have is more along the lines of work_around_BSD_make_bug, work_around_old_rhel_bug, work_around_docker_bug, and work_around_clang_bug.

[lolc]

I do like the policy of noisy workarounds. With workarounds for external flaws I tend to use neutral language though.

[cperciva]

Fair enough. I wouldn't go down this route with something like POSIX_ME_HARDER, because that's a matter of "my design decision is better than your design decision"; but I don't feel that there's any need to be neutral when it comes to things like compilers emitting incorrect code.