mirror of
https://github.com/llvm/llvm-project.git
synced 2025-04-26 07:06:07 +00:00
0f1c1be196
We have a new policy in place making links to private resources something we try to avoid in source and test files. Normally, we'd organically switch to the new policy rather than make a sweeping change across a project. However, Clang is in a somewhat special circumstance currently: recently, I've had several new contributors run into rdar links around test code which their patch was changing the behavior of. This turns out to be a surprisingly bad experience, especially for newer folks, for a handful of reasons: not understanding what the link is and feeling intimidated by it, wondering whether their changes are actually breaking something important to a downstream in some way, having to hunt down strangers not involved with the patch to impose on them for help, accidental pressure from asking for potentially private IP to be made public, etc. Because folks run into these links entirely by chance (through fixing bugs or working on new features), there's not really a set of problematic links to focus on -- all of the links have basically the same potential for causing these problems. As a result, this is an omnibus patch to remove all such links. This was not a mechanical change; it was done by manually searching for rdar, radar, radr, and other variants to find all the various problematic links. From there, I tried to retain or reword the surrounding comments so that we would lose as little context as possible. However, because most links were just a plain link with no supporting context, the majority of the changes are simple removals. Differential Review: https://reviews.llvm.org/D158071
56 lines
1.6 KiB
C
56 lines
1.6 KiB
C
// RUN: %clang_cc1 %s -fsyntax-only -verify -fblocks
|
|
|
|
void take(void*);
|
|
|
|
void test(void) {
|
|
take(^(int x){});
|
|
take(^(int x, int y){});
|
|
take(^(int x, int y){});
|
|
take(^(int x, // expected-note {{previous declaration is here}}
|
|
int x){}); // expected-error {{redefinition of parameter 'x'}}
|
|
|
|
|
|
take(^(int x) { return x+1; });
|
|
|
|
int (^CP)(int) = ^(int x) { return x*x; };
|
|
take(CP);
|
|
|
|
int arg;
|
|
^{return 1;}();
|
|
^{return 2;}(arg); // expected-error {{too many arguments to block call}}
|
|
^(void){return 3;}(1); // expected-error {{too many arguments to block call}}
|
|
^(){return 4;}(arg); // expected-error {{too many arguments to block call}}
|
|
^(int x, ...){return 5;}(arg, arg); // Explicit varargs, ok.
|
|
}
|
|
|
|
int main(int argc, char** argv) {
|
|
^(int argCount) {
|
|
argCount = 3;
|
|
}(argc);
|
|
}
|
|
|
|
void f0(void) {
|
|
^(int, double d, char) {}(1, 1.34, 'a'); // expected-warning {{omitting the parameter name in a function definition is a C23 extension}} \
|
|
// expected-warning {{omitting the parameter name in a function definition is a C23 extension}}
|
|
}
|
|
|
|
void test4(void) {
|
|
int (^f)(void) = ^((x)) { }; // expected-error {{type specifier missing}} expected-error {{type-id cannot have a name}}
|
|
}
|
|
|
|
void test5_helper(void (^)(int, int[*]));
|
|
void test5(void) {
|
|
test5_helper(^(int n, int array[n]) {});
|
|
}
|
|
|
|
// Reduced from a problem on platforms where va_list is an array.
|
|
struct tag {
|
|
int x;
|
|
};
|
|
typedef struct tag array_ty[1];
|
|
void test6(void) {
|
|
void (^block)(array_ty) = ^(array_ty arr) { };
|
|
array_ty arr;
|
|
block(arr);
|
|
}
|