| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
or a pointer to an NSString, emit a code insertion hint that turns it into an Objective-C string. For example:
@class NSString;
@interface Test
+ (void)test:(NSString *)string;
@end
void g(NSString *a);
void f() {
NSString *a = "Foo";
g("Foo");
[Test test:"Foo"];
}
will produce
t.m:10:17: warning: incompatible pointer types initializing 'char [4]', expected 'NSString *'
NSString *a = "Foo";
^~~~~
@
t.m:11:5: warning: incompatible pointer types passing 'char [4]', expected 'NSString *'
g("Foo");
^~~~~
@
t.m:12:14: warning: incompatible pointer types sending 'char [4]', expected 'NSString *'
[Test test:"Foo"];
^~~~~
@
3 diagnostics generated.
llvm-svn: 86665
|
| |
|
|
|
|
| |
has a defualt argument then add a fixit hint that removes the default argument. Fixes PR5444.
llvm-svn: 86659
|
| |
|
|
|
|
| |
- 'for i in $(find . -type f); do sed -e 's#\(RUN:.*[^ ]\) *&& *$#\1#g' $i | FileUpdate $i; done', for the curious.
llvm-svn: 86430
|
| |
|
|
|
|
|
|
|
|
|
| |
get_origin->x
where get_origin is actually a function and the user has forgotten the
parentheses. Instead of giving a lame note for the fix-it, give a
full-fledge error, early, then build the call expression to try to
recover.
llvm-svn: 86238
|
| |
|
|
|
|
| |
binary operators.
llvm-svn: 85153
|
| |
|
|
|
|
| |
though?
llvm-svn: 71955
|
| |
|
|
| |
llvm-svn: 68454
|
| |
|
|
| |
llvm-svn: 68395
|
| |
|
|
| |
llvm-svn: 68349
|
| |
|
|
|
|
|
| |
applies fix-its to error messages that occur at that specific location
in the program.
llvm-svn: 68342
|
|
|
llvm-svn: 68325
|
