aee4925507
Based on post-commit review discussion on 2bd84938470bf2e337801faafb8a67710f46429d with Richard Smith. Other uses of forcing HasEmptyPlaceHolder to false seem OK to me - they're all around pointer/reference types where the pointer/reference token will appear at the rightmost side of the left side of the type name, so they make nested types (eg: the "int" in "int *") behave as though there is a non-empty placeholder (because the "*" is essentially the placeholder as far as the "int" is concerned). This was originally committed in 277623f4d5a672d707390e2c3eaf30a9eb4b075c Reverted in f9ad1d1c775a8e264bebc15d75e0c6e5c20eefc7 due to breakages outside of clang - lldb seems to have some strange/strong dependence on "char [N]" versus "char[N]" when printing strings (not due to that name appearing in DWARF, but probably due to using clang to stringify type names) that'll need to be addressed, plus a few other odds and ends in other subprojects (clang-tools-extra, compiler-rt, etc).
35 lines
796 B
C++
35 lines
796 B
C++
// RUN: %clang_cc1 -std=c++1z -verify %s -Wpedantic
|
|
|
|
struct X {
|
|
X(int);
|
|
X(const X&) = delete;
|
|
};
|
|
|
|
int array() {
|
|
static int arr[3] = {};
|
|
auto [a, b, c] = arr;
|
|
static_assert(&a != &arr[0]);
|
|
|
|
using I3 = int[3];
|
|
auto [a2, b2, c2] = I3{1, 2, 3};
|
|
|
|
using X3 = X[3];
|
|
auto [a3, b3, c3] = X3{1, 2, 3};
|
|
|
|
auto &[d, e] = arr; // expected-error {{type 'int[3]' decomposes into 3 elements, but only 2 names were provided}}
|
|
auto &[f, g, h, i] = arr; // expected-error {{type 'int[3]' decomposes into 3 elements, but 4 names were provided}}
|
|
|
|
auto &[r0, r1, r2] = arr;
|
|
const auto &[cr0, cr1, cr2] = arr;
|
|
|
|
static_assert(&arr[0] == &r0);
|
|
static_assert(&arr[0] == &cr0);
|
|
|
|
using T = int;
|
|
using T = decltype(r0);
|
|
using U = const int;
|
|
using U = decltype(cr0);
|
|
|
|
return r1 + cr2;
|
|
}
|