summaryrefslogtreecommitdiffstats
path: root/clang/lib/Frontend/CompilerInvocation.cpp
diff options
context:
space:
mode:
authorJordan Rose <jordan_rose@apple.com>2015-01-16 23:04:31 +0000
committerJordan Rose <jordan_rose@apple.com>2015-01-16 23:04:31 +0000
commita34d04d35e72c9104c32e2f772b8bccab7f0cd33 (patch)
treed11a22b32d20a9434fbcff50b82962ee4dda18e5 /clang/lib/Frontend/CompilerInvocation.cpp
parent16ba553f754a6ab6c934deaa6232be1cb74db904 (diff)
downloadbcm5719-llvm-a34d04d35e72c9104c32e2f772b8bccab7f0cd33.tar.gz
bcm5719-llvm-a34d04d35e72c9104c32e2f772b8bccab7f0cd33.zip
Suggest objc_method_family(none) for a property named -newFoo or similar.
As mentioned in the previous commit, if a property (declared with @property) has a name that matches a special Objective-C method family, the getter picks up that family despite being declared by the property. The most correct way to solve this problem is to add the 'objc_method_family' attribute to the getter with an argument of 'none', which unfortunately requires an explicit declaration of the getter. This commit adds a note to the existing error (ARC) or warning (MRR) for such a poorly-named property that suggests the solution; if there's already a declaration of the getter, it even includes a fix-it. llvm-svn: 226339
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud