You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Objective-c categories are a way of extending a given objective-c class. It almost feels like categories are used to organize various sections of their codebase. As a result, there are a lot of categories in the apple frameworks.
In #1750 I added better inheritance support for the binding generation but didn't add the impl blocks for the traits generated from the Objective-c categories.
It's unclear to me how to best implement this because a given class has no reference to the classes it implements. The only reference to the classes are from the categories to the classes they extend.
Adding support for categories (even if ugly or with manual steps in the Builder configuration) would be much appreciated. For instance, NSString and NSMutableString have their convenient APIs entirely in categories, making it very difficult to work with some of the most primitive classes in apple frameworks.
Adding support for categories (even if ugly or with manual steps in the Builder configuration) would be much appreciated. For instance, NSString and NSMutableString have their convenient APIs entirely in categories, making it very difficult to work with some of the most primitive classes in apple frameworks.
I misinterpreted the purpose of this bug, and now realize that categories are supported: you have to allowlist CLASS_CATEGORY, which I didn't expect.
Objective-c categories are a way of extending a given objective-c class. It almost feels like categories are used to organize various sections of their codebase. As a result, there are a lot of categories in the apple frameworks.
In #1750 I added better inheritance support for the binding generation but didn't add the impl blocks for the traits generated from the Objective-c categories.
It's unclear to me how to best implement this because a given class has no reference to the classes it implements. The only reference to the classes are from the categories to the classes they extend.
Input C/C++ Header
Bindgen Invocation
Actual Results
Expected Results
impl Foo_BarCategory for Bar {}
is missing and should be something like the following:The text was updated successfully, but these errors were encountered: