e5c7904fa0
It has been reported to that the current clang errors for, specifically, static_assert in export contexts are a serious blocker to adoption of modules in some cases. There is also implementation divergence with GCC and MSVC allowing the constructs mentioned below where clang currently rejects them with an error. The category of errors [for declarations in an exported context] is: (unnamed, static_assert, empty and asm decls). These are now permitted after P2615R1 which was approved by WG21 as a DR (and thus should be applied to C++20 as well). This patch removes these diagnostics and amends the testsuite accordingly. Differential Revision: https://reviews.llvm.org/D152946
32 lines
1007 B
C++
32 lines
1007 B
C++
// Based on C++20 10.2 example 1.
|
|
|
|
// RUN: rm -rf %t
|
|
// RUN: mkdir -p %t
|
|
// RUN: split-file %s %t
|
|
|
|
// RUN: %clang_cc1 -std=c++20 -emit-module-interface %t/std-10-2-ex1-tu1.cpp \
|
|
// RUN: -pedantic-errors -verify -o %t/m1.pcm
|
|
|
|
//--- std-10-2-ex1.h
|
|
export int x;
|
|
|
|
//--- std-10-2-ex1-tu1.cpp
|
|
module;
|
|
|
|
#include "std-10-2-ex1.h"
|
|
// expected-error@std-10-2-ex1.h:* {{export declaration can only be used within a module purview}}
|
|
|
|
export module M1;
|
|
export namespace {} // expected-error {{anonymous namespaces cannot be exported}}
|
|
export namespace { // expected-error {{anonymous namespaces cannot be exported}}
|
|
int a1;
|
|
}
|
|
namespace { // expected-note {{anonymous namespace begins here}}
|
|
export int a2; // expected-error {{export declaration appears within anonymous namespace}}
|
|
}
|
|
export static int b; // expected-error {{declaration of 'b' with internal linkage cannot be exported}}
|
|
export int f(); // OK
|
|
|
|
export namespace N {} // namespace N
|
|
export using namespace N; // No diagnostic after P2615R1 DR
|