-
Notifications
You must be signed in to change notification settings - Fork 67
Protocol methods missing from classes #1487
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Nevermind, turns out |
Do I need to do something special in my config to pick up the protocol? I synced to the hash with that fix, and still don't have the methods described in the original issue description. |
@stuartmorgan No, you shouldn't need to do anything. Can you send me your config? I'll see if I can repro. There might be a second bug here. |
My actual repro case is here, but I think this should be the relevant parts (I haven't set up a clean test with this though):
|
Ah ok. The issue is that the protocol is not being included by the config. I think probably the correct behavior here is that protocols that an interface conforms to should always be included in the interface's methods, regardless of the filters (or rather they should go through the same method filtering as ordinary methods). But we should only generate bindings for the protocol itself if the protocol is included in the filter. |
(There's a bit of related discussion in #1462, but this is a distinct issue.)
I'm unable to call methods on an object that come from a protocol, even when they are required methods. The concrete case I hit is:
In Obj-C code I can then of course call:
But that method simply doesn't exist on
AVAsset
in the ffigen output, even though it's an explicit part of the public interface.The text was updated successfully, but these errors were encountered: