aee4925507
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).
28 lines
880 B
Objective-C
28 lines
880 B
Objective-C
// Test this without pch.
|
|
// RUN: %clang_cc1 -fblocks -include %S/objc_exprs.h -fsyntax-only -verify %s
|
|
|
|
// Test with pch.
|
|
// RUN: %clang_cc1 -x objective-c-header -emit-pch -fblocks -o %t %S/objc_exprs.h
|
|
// RUN: %clang_cc1 -fblocks -include-pch %t -fsyntax-only -verify %s
|
|
|
|
// Expressions
|
|
int *A1 = (objc_string)0; // expected-warning {{aka 'NSString *'}}
|
|
|
|
char A2 = (objc_encode){}; // expected-error {{not a compile-time constant}} \
|
|
expected-warning {{char[2]}}
|
|
|
|
int *A3 = (objc_protocol)0; // expected-warning {{aka 'Protocol *'}}
|
|
|
|
|
|
// Types.
|
|
int *T0 = (objc_id_protocol_ty)0; // expected-warning {{aka 'id<foo>'}}
|
|
|
|
int *T1 = (objc_interface_ty)0; // expected-warning {{aka 'itf *'}}
|
|
int *T2 = (objc_qual_interface_ty)0; // expected-warning {{aka 'itf<foo> *'}}
|
|
|
|
objc_selector_noArgs s1;
|
|
objc_selector_oneArg s2;
|
|
objc_selector_twoArg s3;
|
|
|
|
|