-
Notifications
You must be signed in to change notification settings - Fork 707
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
Global enum in the wrong namespace #888
Comments
Thanks for the bug report! |
First of all, sorry for taking so long to look at this. So this is because the code in However, this is not true for this case, since we jump to the struct definition when we see the first declaration. Making Thanks a lot for the report! |
Huh, that actually worked quite easily... Shrug. Will submit a pull request. |
…s until we parse it. Fixes rust-lang#888
…s until we parse it. This ensures that we see all the relevant types that are defined when parsing the definition, avoiding problems like rust-lang#888. Fixes rust-lang#888
I opened #926 with the fix for this. |
@emilio No worries! I've been busy with other stuff anyways. I'm just happy to help, even if its just with a bug report :) Keep up the good work! |
…s until we parse it. This ensures that we see all the relevant types that are defined when parsing the definition, avoiding problems like rust-lang#888. Fixes rust-lang#888
ir: When something has a definition, return unresolved type references until we parse it. This fixes #888
Hello,
While attempting to generate rust bindings for Halide, I think that I encountered a bug. It seems like when the declaration and definition of a type occurs in two separate namespace 'wrappers' and the definition uses an
enum
from the global scope some bogus rust code is generated.Input C/C++ Header
Bindgen Invocation
Actual Results
The generated bindings end up like this:
and/or
Expected Results
I expected the member variable
b
to be of the typeroot::a
rather thanroot::Halide::a
since it is technically defined in the global namespace rather than inside theHalide
namespace.The text was updated successfully, but these errors were encountered: