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
85 lines
1.4 KiB
Objective-C
85 lines
1.4 KiB
Objective-C
// RUN: %clang_cc1 -fsyntax-only -verify -fblocks %s
|
|
|
|
void takevoidptr(void*);
|
|
|
|
|
|
@interface Foo
|
|
- iMethod;
|
|
+ cMethod;
|
|
@end
|
|
|
|
@interface A
|
|
+ superClassMethod;
|
|
- (void)instanceMethod;
|
|
@end
|
|
|
|
@interface B : A
|
|
- (void)instanceMethod;
|
|
+ classMethod;
|
|
@end
|
|
|
|
@implementation B
|
|
|
|
- (void)instanceMethod {
|
|
[super iMethod]; // expected-warning{{'A' may not respond to 'iMethod'}}
|
|
|
|
// Use of super in a block is ok and does codegen to the right thing.
|
|
takevoidptr(^{
|
|
[super instanceMethod];
|
|
});
|
|
}
|
|
|
|
+ classMethod {
|
|
[super cMethod]; // expected-warning{{method '+cMethod' not found (return type defaults to 'id')}}
|
|
|
|
id X[] = { [ super superClassMethod] };
|
|
id Y[] = {
|
|
[ super.superClassMethod iMethod],
|
|
super.superClassMethod,
|
|
(id)super.superClassMethod // not a cast of super
|
|
};
|
|
return 0;
|
|
}
|
|
@end
|
|
|
|
@interface XX
|
|
- m;
|
|
@end
|
|
|
|
void f(id super) {
|
|
[super m];
|
|
}
|
|
void f0(int super) {
|
|
[super m]; // expected-warning{{receiver type 'int' is not 'id'}}
|
|
}
|
|
void f1(id puper) { // expected-note {{'puper' declared here}}
|
|
[super m]; // expected-error{{use of undeclared identifier 'super'}}
|
|
}
|
|
|
|
typedef Foo super;
|
|
|
|
typedef Foo FooTD;
|
|
|
|
void test(void) {
|
|
[FooTD cMethod];
|
|
[super cMethod];
|
|
}
|
|
|
|
struct SomeStruct {
|
|
int X;
|
|
};
|
|
|
|
int test2(void) {
|
|
struct SomeStruct super = { 0 };
|
|
return super.X;
|
|
}
|
|
|
|
int test3(void) {
|
|
id super = 0;
|
|
[(B*)super instanceMethod];
|
|
int *s1 = (int*)super;
|
|
|
|
id X[] = { [ super superClassMethod] };
|
|
return 0;
|
|
}
|