diff options
author | Alex Lorenz <arphaman@gmail.com> | 2019-01-09 22:31:37 +0000 |
---|---|---|
committer | Alex Lorenz <arphaman@gmail.com> | 2019-01-09 22:31:37 +0000 |
commit | 4e3c0bdf6fa7dbc1df282e36ea41f3dc9864a73c (patch) | |
tree | 462118bd3286fa491eb84144b3852ad3c20d87be /libcxx/test/std/utilities/tuple/tuple.tuple/TupleFunction.pass.cpp | |
parent | c58fbe3c7116134d21f6aa844cc00e16e9dc8c5f (diff) | |
download | bcm5719-llvm-4e3c0bdf6fa7dbc1df282e36ea41f3dc9864a73c.tar.gz bcm5719-llvm-4e3c0bdf6fa7dbc1df282e36ea41f3dc9864a73c.zip |
[ObjC] Allow the use of implemented unavailable methods from within
the @implementation context
In Objective-C, it's common for some frameworks to mark some methods like init
as unavailable in the @interface to prohibit their usage. However, these
frameworks then often implemented said method and refer to it in another method
that acts as a factory for that object. The recent change to how messages to
self are type checked in clang (r349841) introduced a regression which started
to prohibit this pattern with an X is unavailable error. This commit addresses
the aforementioned regression.
rdar://47134898
Differential Revision: https://reviews.llvm.org/D56469
llvm-svn: 350768
Diffstat (limited to 'libcxx/test/std/utilities/tuple/tuple.tuple/TupleFunction.pass.cpp')
0 files changed, 0 insertions, 0 deletions