bcm5719-llvm/clang/test/SemaObjC/objc-literal-comparison.m, branch meklort-10.0.0

Objective-C. revert patch for rdar://17554063.

2014-10-28T18:28:16+00:00

llvm-svn: 220812

Objective-C ARC. Use of non-retain/autorelease API

2014-08-08T17:31:14+00:00

for building Objective-C array literals in ARC mode. rdar://17554063 llvm-svn: 215232

Objective-C arc. Switch the Objective-C dictionary literal in ARC mode

2014-08-07T20:57:35+00:00

to use non-retain/autorelease API variants of ObjC objects. wip. rdar://17554063 llvm-svn: 215146

Objective-C ARC. More code for Objective-C's

2014-08-06T23:40:31+00:00

new APIs for literals. nfc. wip. rdar://17554063 llvm-svn: 215043

Sema: Unnest early exit and remove an unnecessary bad cast.

2013-02-15T15:17:50+00:00

cast doesn't look through sugar, getAs does. Fixes PR15257. llvm-svn: 175272

-Wobjc-literal-compare: look through implicit casts.

2012-11-09T23:55:21+00:00

This warning was failing to fire under ARC because of the implicit lifetime casts added around the object literal expression. , again. llvm-svn: 167648

-Wobjc-literal-compare: don't warn when comparing against nil.

2012-07-17T17:46:48+00:00

Checks against nil often appear as guards in macros, and comparing Objective-C literals to nil has well-defined behavior (if tautological). On OS X, 'nil' has not been typed as 'id' since 10.6 (possibly earlier), so the warning was already not firing, but other runtimes continue to use ((id)0) or some variant. This change accepts comparisons to any null pointer; to keep it simple, it looks through all casts (not just casts to 'id'). PR13276 llvm-svn: 160379

Add -Wobjc-string-compare under -Wobjc-literal-compare.

2012-07-17T17:46:44+00:00

Suggested by Ted, since string literal comparison is at least slightly more sensible than comparison of runtime literals. (Ambiguous language on developer.apple.com implies that strings are guaranteed to be uniqued within a translation unit and possibly across a linked binary.) llvm-svn: 160378

Now that -Wobjc-literal-compare is a warning, put the fixit on a note.

2012-07-17T17:46:40+00:00

Recovering as if the user had actually called -isEqual: is a bit too far from the semantics of the program as written, /even though/ it's probably what they intended. llvm-svn: 160377

Downgrade the "direct comparison" error for ObjC literals to a warning.

2012-07-09T16:54:44+00:00

Chris pointed out that while the comparison is certainly problematic and does not have well-defined behavior, it isn't any worse than some of the other abuses that we merely warn about and doesn't need to make the compilation fail. Revert the release notes change (r159766) now that this is just a new warning. llvm-svn: 159939