llvm-project/clang/test/Modules/cxx20-10-2-ex3.cpp

// Based on C++20 10.2 example 3.

// RUN: %clang_cc1 -std=c++20 -emit-module-interface %s -o %t

export module M;
struct S;
export using T = S; // OK, exports name T denoting type S

// expected-no-diagnostics
[C++20][Modules] Adjust handling of exports of namespaces and using-decls. This adjusts the handling for: export module M; export namespace {}; export namespace N {}; export using namespace N; In the first case, we were allowing empty anonymous namespaces as part of an extension allowing empty top-level entities, but that seems inappropriate in this case, since the linkage would be internal for the anonymous namespace. We now report an error for this. The second case was producing a warning diagnostic that this was accepted as an extension - however the C++20 standard does allow this as well-formed. In the third case we keep the current practice that this is accepted with a warning (as an extension). The C++20 standard says it's an error. We also ensure that using decls are only applied to items with external linkage. This adjusts error messages for exports involving redeclarations in modules to be more specific about the reason that the decl has been rejected. Differential Revision: https://reviews.llvm.org/D122119 2021-05-04 16:56:02 +08:00			`// Based on C++20 10.2 example 3.`

Use writable temporary file for test compiler output instead of hardcoded name. NFCI. 2022-04-09 01:57:20 +08:00			`// RUN: %clang_cc1 -std=c++20 -emit-module-interface %s -o %t`
[C++20][Modules] Adjust handling of exports of namespaces and using-decls. This adjusts the handling for: export module M; export namespace {}; export namespace N {}; export using namespace N; In the first case, we were allowing empty anonymous namespaces as part of an extension allowing empty top-level entities, but that seems inappropriate in this case, since the linkage would be internal for the anonymous namespace. We now report an error for this. The second case was producing a warning diagnostic that this was accepted as an extension - however the C++20 standard does allow this as well-formed. In the third case we keep the current practice that this is accepted with a warning (as an extension). The C++20 standard says it's an error. We also ensure that using decls are only applied to items with external linkage. This adjusts error messages for exports involving redeclarations in modules to be more specific about the reason that the decl has been rejected. Differential Revision: https://reviews.llvm.org/D122119 2021-05-04 16:56:02 +08:00
			`export module M;`
			`struct S;`
			`export using T = S; // OK, exports name T denoting type S`

			`// expected-no-diagnostics`