-
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
Panic in bindgen: "Not an item" #1127
Comments
Hello again, template <typename> struct A;
template <typename, typename, bool> struct _Map_base;
template <typename _Pair, typename _Traits>
struct _Map_base<_Pair, _Traits, true> {
using __hashtable_base = A<_Traits>;
using key_type = typename __hashtable_base::key_type;
using mapped_type = typename _Pair::type;
mapped_type &at(const key_type &);
};
template <typename _Pair, typename _Traits>
auto _Map_base<_Pair, _Traits, true>::at(const key_type &) -> mapped_type & {} |
Thanks so much for the test-case, makes it much easier :) |
I happen to be hitting this today, so I'm investigating a bit. |
emilio
added a commit
to emilio/rust-bindgen
that referenced
this issue
Oct 31, 2017
…ng AlreadyResolved. The item may come from a recursive check down the stack, and as we say there: > Unchecked because we haven't finished this type yet. Fixes rust-lang#1127
emilio
added a commit
to emilio/rust-bindgen
that referenced
this issue
Oct 31, 2017
…ng AlreadyResolved. The item may come from a recursive check down the stack, and as we say there: > Unchecked because we haven't finished this type yet. Fixes rust-lang#1127
Fix at #1128 |
bors-servo
pushed a commit
that referenced
this issue
Oct 31, 2017
ir: We can't guarantee the type to be in the item map while propagating AlreadyResolved The item may come from a recursive check down the stack, and as we say there: > Unchecked because we haven't finished this type yet. Fixes #1127
bors-servo
pushed a commit
that referenced
this issue
Oct 31, 2017
ir: We can't guarantee the type to be in the item map while propagating AlreadyResolved The item may come from a recursive check down the stack, and as we say there: > Unchecked because we haven't finished this type yet. Fixes #1127
Thanks a lot for this super fast fix! |
emilio
added a commit
to emilio/rust-bindgen
that referenced
this issue
Oct 31, 2017
…ng AlreadyResolved. The item may come from a recursive check down the stack, and as we say there: > Unchecked because we haven't finished this type yet. Fixes rust-lang#1127
bors-servo
pushed a commit
that referenced
this issue
Oct 31, 2017
ir: We can't guarantee the type to be in the item map while propagating AlreadyResolved The item may come from a recursive check down the stack, and as we say there: > Unchecked because we haven't finished this type yet. Fixes #1127
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am trying to wrap some large c++ framework and bumped into the following issue using bindgen
0.31.1
. It is a panic in bindgen. Frankly, I'm not sure what exactly is going on and thecreduced
sample is still quite cryptic to me. The panic message seems similar to issue #67. Thanks a lot in advance and for the fantastic thing that bindgen is! Here it goes:Input C/C++ Header
Bindgen Invocation
Actual Results
Expected Results
I don't really expect bindgen to generate bindings for
c++
code which I don't understand myself. But I would hope for a hint on what is going wrong.The text was updated successfully, but these errors were encountered: