================
@@ -0,0 +1,84 @@
+// This file tests the coro_structured_concurrency attribute semantics.
+// RUN: %clang_cc1 -std=c++20 -disable-llvm-passes -emit-llvm %s -o - |
FileCheck %s
+
+#include "Inputs/coroutine.h"
+#include "Inputs/utility.h"
+
+template <typename T>
+struct [[clang::coro_structured_concurrency]] Task {
----------------
vogelsgesang wrote:
Afaict, this particular `Task` can also be annotated using
`coro_only_destroy_when_complete`?
I guess many libraries would want to use both `coro_structured_concurrency` /
`coro_inplace_task` and `coro_only_destroy_when_complete`. Do those
optimizations interact well with each other? Does it make sense to add a test
case which tests both attributes together?
https://github.com/llvm/llvm-project/pull/94693
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
