-
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
Properly handle namespaces for enum configuration options #1162
Conversation
Can you add a note to the unreleased section of the changelog about this breaking change? Thanks! |
And did it fix the issues you were seeing in that other bug? |
...by using canonical_path rather than canonical_name. Fixes #1125.
Added a note to the changelog. I haven't had a chance to test the other issue yet, I may get to it today (but may not). |
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, thanks!
@bors-servo r+ |
📌 Commit 89efc23 has been approved by |
☀️ Test successful - status-travis |
rather than its "canonical name", which does not. This is a breaking change | ||
that requires callers which target a namespaced C++ enum to call e.g. | ||
`bitfield_enum("<namespace>::<enum_name>")` rather than e.g. | ||
`bitfield_enum("<enum_name>")`. [#1162][] |
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.
Thanks!
...by using canonical_path rather than canonical_name.
Fixes #1125.
r? @emilio