mirror of
https://github.com/llvm/llvm-project.git
synced 2025-04-27 15:16:08 +00:00
ec117158a3
Now in libcxx and clang, all the coroutine components are defined in std::experimental namespace. And now the coroutine TS is merged into C++20. So in the working draft like N4892, we could find the coroutine components is defined in std namespace instead of std::experimental namespace. And the coroutine support in clang seems to be relatively stable. So I think it may be suitable to move the coroutine component into the experiment namespace now. This patch would make clang lookup coroutine_traits in std namespace first. For the compatibility consideration, clang would lookup in std::experimental namespace if it can't find definitions in std namespace. So the existing codes wouldn't be break after update compiler. And in case the compiler found std::coroutine_traits and std::experimental::coroutine_traits at the same time, it would emit an error for it. The support for looking up std::experimental::coroutine_traits would be removed in Clang16. Reviewed By: lxfind, Quuxplusone Differential Revision: https://reviews.llvm.org/D108696
21 lines
714 B
C++
21 lines
714 B
C++
// RUN: %clang_cc1 -fsyntax-only -verify -fcoroutines-ts %s
|
|
// RUN: %clang_cc1 -fsyntax-only -verify -std=c++20 %s
|
|
// RUN: %clang_cc1 -fsyntax-only -verify -DERRORS %s
|
|
|
|
// Check that we don't crash when using __builtin_coro_* without the fcoroutine-ts or -std=c++20 option
|
|
|
|
#ifdef ERRORS
|
|
// expected-error@#A{{use of undeclared identifier '__builtin_coro_done'}}
|
|
// expected-error@#B{{use of undeclared identifier '__builtin_coro_id'}}
|
|
// expected-error@#C{{use of undeclared identifier '__builtin_coro_alloc'}}
|
|
#else
|
|
// expected-no-diagnostics
|
|
#endif
|
|
|
|
int main() {
|
|
void *co_h;
|
|
bool d = __builtin_coro_done(co_h); // #A
|
|
__builtin_coro_id(32, 0, 0, 0); // #B
|
|
__builtin_coro_alloc(); // #C
|
|
}
|