-
Notifications
You must be signed in to change notification settings - Fork 43
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
Typedef support #359
Comments
Yes, this would be a good feature, especially when structs have multiple names. We should still probably only generate typedefs that are being used somewhere in the generated code. |
I think that only generating typedefs that are being used somewhere is a good default, but the option to include all typedefs should be available. |
From what I see, having typedefs that aren't being used anywhere in the generated bindings would be useless, even if generated. Can you point out some use cases for when this would be helpful? Otherwise simply generating only the required typedefs would be much simpler. |
I guess you are right. I can't think of a situation where that would be useful |
Now that Dart 2.13 has non-function typedef support I think it would be reasonable to translate C typedefs to Dart typedefs. In a library I'm attempting to wrap it has a lot of simple typedefs, which makes it hard when I'm trying to find some type under a certain name as specified in the headers, only to find it has a different name in the dart library generated by ffigen.
The text was updated successfully, but these errors were encountered: