-
Notifications
You must be signed in to change notification settings - Fork 746
Behavior change for non-whitelisted types referenced by method #834
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
I guess this is not really a bug, but a breaking behavior change which we should mention somewhere when people upgrade. (Do we have changelog?) This definitely breaks Stylo, but it is probably because we are relying on something which we shouldn't rely on, and this can be easily fixed by simply whitelisting those types. So I guess this isn't really an issue. |
And I actually think the new behavior is probably more desirable (because it would generate fewer types that we don't need). We should probably add this to the test suite so that we don't regress this behavior. |
Note that I'm regressing this in #835 |
…ted_items() for code generation. This standardizes the behavior change at rust-lang#834, but without regressions. I've added a few more tests for rust-lang#833 here.
And my idea is to un-regress it in #836. |
…ted_items() for code generation. This standardizes the behavior change at rust-lang#834, but without regressions. I've added a few more tests for rust-lang#833 here.
…ted_items() for code generation. This standardizes the behavior change at rust-lang#834, but without regressions. I've added a few more tests for rust-lang#833 here.
Input C/C++ Header
Bindgen Invocation
Actual Results
Expected Results
Not really expected result, but before #827, it generates
The text was updated successfully, but these errors were encountered: