llvm-project/clang/test/PCH/cxx1y-default-initializer.cpp

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

47 lines
1.2 KiB
C++
Raw Normal View History

// RUN: %clang_cc1 -pedantic -std=c++1y -include %s -include %s -verify %s
// RUN: %clang_cc1 -pedantic -std=c++1y -emit-pch -o %t.1 %s
// RUN: %clang_cc1 -pedantic -std=c++1y -include-pch %t.1 -emit-pch -o %t.2 %s
// RUN: %clang_cc1 -pedantic -std=c++1y -include-pch %t.2 -verify %s
#ifndef HEADER_1
#define HEADER_1
struct A {
int x;
int y = 3;
int z = x + y;
};
template<typename T> constexpr A make() { return A {}; }
template<typename T> constexpr A make(T t) { return A { t }; }
struct B {
int z1, z2 = z1;
constexpr B(int k) : z1(k) {}
};
template<typename T> struct C {
constexpr C() {}
T c = T();
struct U {};
};
// Instantiate C<int> but not the default initializer.
C<int>::U ciu;
#elif !defined(HEADER_2)
#define HEADER_2
// Instantiate the default initializer now, should create an update record.
C<int> ci;
#else
static_assert(A{}.z == 3, "");
static_assert(A{1}.z == 4, "");
[c++20] Implement semantic restrictions for C++20 designated initializers. This has some interesting interactions with our existing extensions to support C99 designated initializers as an extension in C++. Those are resolved as follows: * We continue to permit the full breadth of C99 designated initializers in C++, with the exception that we disallow a partial overwrite of an initializer with a non-trivially-destructible type. (Full overwrite is OK, because we won't run the first initializer at all.) * The C99 extensions are disallowed in SFINAE contexts and during overload resolution, where they could change the meaning of valid programs. * C++20 disallows reordering of initializers. We only check for that for the simple cases that the C++20 rules permit (designators of the form '.field_name =' and continue to allow reordering in other cases). It would be nice to improve this behavior in future. * All C99 designated initializer extensions produce a warning by default in C++20 mode. People are going to learn the C++ rules based on what Clang diagnoses, so it's important we diagnose these properly by default. * In C++ <= 17, we apply the C++20 rules rather than the C99 rules, and so still diagnose C99 extensions as described above. We continue to accept designated C++20-compatible initializers in C++ <= 17 silently by default (but naturally still reject under -pedantic-errors). This is not a complete implementation of P0329R4. In particular, that paper introduces new non-C99-compatible syntax { .field { init } }, and we do not support that yet. This is based on a previous patch by Don Hinton, though I've made substantial changes when addressing the above interactions. Differential Revision: https://reviews.llvm.org/D59754 llvm-svn: 370544
2019-08-31 06:52:55 +08:00
static_assert(A{.y = 5}.z == 5, ""); // expected-warning {{C++20}}
static_assert(A{3, .y = 1}.z == 4, ""); // expected-warning {{C99}} expected-note {{here}}
static_assert(make<int>().z == 3, "");
static_assert(make<int>(12).z == 15, "");
static_assert(C<int>().c == 0, "");
#endif