-
Notifications
You must be signed in to change notification settings - Fork 745
Declare precedence on enum types #1272
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
Conversation
If an enum matched a pattern for rustified enum and constified module enum, then rust code would fail to compile with "ambiguous associated type" error. We fix the error by giving constified module enum "higher precedence". Fixes issue rust-lang#1198
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, but CI needs to be green.
Thanks!
@@ -0,0 +1,18 @@ | |||
/* automatically generated by rust-bindgen */ | |||
|
|||
#![allow(dead_code, non_snake_case, non_camel_case_types, non_upper_case_globals)] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like CI is not really happy about this (needs expectations for other libclang versions). But does this need to be really a libclang-3.9+ test?
@bors-servo r+ Thanks! |
📌 Commit 8c9b3ab has been approved by |
Declare precedence on enum types Fixes issue #1198 where an enum matches the pattern for multiple enum types, such as constified module enum AND rustified enum. Documents precedence in `Builder` doc comment.
☀️ Test successful - status-travis |
Fixes issue #1198 where an enum matches the pattern for multiple enum types, such as constified module enum AND rustified enum.
Documents precedence in
Builder
doc comment.