For the archives, here's said patch: https://reviews.llvm.org/D56816
(Thanks!)
On Wed, Jan 16, 2019 at 5:26 PM Alex L wrote:
> Hi,
>
> We are planning to fix this issue by not checking if the method is
> defined. I will post a patch this week.
>
> Cheers,
> Alex
>
> On Fri, 11 Jan 2019 at 10:26
Hi,
We are planning to fix this issue by not checking if the method is defined.
I will post a patch this week.
Cheers,
Alex
On Fri, 11 Jan 2019 at 10:26, Alex L wrote:
> Thanks, we might have similar cases in our code base as well. We'll see if
> we can fix that too.
>
> On Fri, 11 Jan 2019 at
Thanks, we might have similar cases in our code base as well. We'll see if
we can fix that too.
On Fri, 11 Jan 2019 at 06:13, Nico Weber wrote:
> Here's some user feedback on this new feature.
>
> It looks like the warning is only suppressed if `init` has a definition in
> the @interface block.
Here's some user feedback on this new feature.
It looks like the warning is only suppressed if `init` has a definition in
the @interface block. In the 4 cases where we saw this warning fire after
r349841, it still fires after this change because in all 4 cases a class
marked init as unavailable in
Author: arphaman
Date: Wed Jan 9 14:31:37 2019
New Revision: 350768
URL: http://llvm.org/viewvc/llvm-project?rev=350768&view=rev
Log:
[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 metho
