Based on post-commit review discussion on2bd8493847with 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 in277623f4d5Reverted inf9ad1d1c77due 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).
19 lines
977 B
C++
19 lines
977 B
C++
// RUN: %clang_cc1 -std=c++2a -verify %s
|
|
|
|
template<typename T> requires (sizeof(T) >= 4 && sizeof(T) <= 10)
|
|
// expected-note@-1{{because 'sizeof(char[20]) <= 10' (20 <= 10) evaluated to false}}
|
|
// expected-note@-2{{because 'sizeof(char) >= 4' (1 >= 4) evaluated to false}}
|
|
void foo() requires (sizeof(T) <= 8) {}
|
|
// expected-note@-1{{candidate template ignored: constraints not satisfied [with T = char]}}
|
|
// expected-note@-2{{candidate template ignored: constraints not satisfied [with T = char[9]]}}
|
|
// expected-note@-3{{candidate template ignored: constraints not satisfied [with T = char[20]]}}
|
|
// expected-note@-4{{because 'sizeof(char[9]) <= 8' (9 <= 8) evaluated to false}}
|
|
|
|
void bar() {
|
|
foo<char>(); // expected-error{{no matching function for call to 'foo'}}
|
|
foo<int>();
|
|
foo<unsigned long long int>();
|
|
foo<char[9]>(); // expected-error{{no matching function for call to 'foo'}}
|
|
foo<char[20]>(); // expected-error{{no matching function for call to 'foo'}}
|
|
}
|