Coroutines tests are failing when building with Clang because libstdc++ headers want a -fcoroutines option enabled, which Clang doesn't have (it's got -fcoroutines-ts). There are two solutions, and I think they should happen in parallel.
Make all Clang-based coro-aware CI use libc++, which doesn't have this issue. Simple and can be done internally, but adds to the CI load.
File a bug with libstdc++ to check for Clang flag as well. Ultimately transparent to range-v3 and improves the dev ecosystem, but it could take time (will it be a GCC 10 hotfix? Even if it is, will GitHub's GCC 10 get this hotfix?).
Coroutines tests are failing when building with Clang because libstdc++ headers want a
-fcoroutines
option enabled, which Clang doesn't have (it's got-fcoroutines-ts
). There are two solutions, and I think they should happen in parallel.