Skip to content
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

Merged
merged 1 commit into from Nov 28, 2017

Conversation

Projects
None yet
5 participants
@tamird
Copy link
Contributor

tamird commented Nov 27, 2017

...by using canonical_path rather than canonical_name.

Fixes #1125.

r? @emilio

@fitzgen

This comment has been minimized.

Copy link
Member

fitzgen commented Nov 27, 2017

Can you add a note to the unreleased section of the changelog about this breaking change? Thanks!

@fitzgen

This comment has been minimized.

Copy link
Member

fitzgen commented Nov 27, 2017

And did it fix the issues you were seeing in that other bug?

Properly handle namespaces for enum configuration options
...by using canonical_path rather than canonical_name.

Fixes #1125.

@tamird tamird force-pushed the tamird:enum-naming-consistency branch from 27545e2 to 89efc23 Nov 27, 2017

@tamird

This comment has been minimized.

Copy link
Contributor Author

tamird commented Nov 27, 2017

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).

@emilio

emilio approved these changes Nov 28, 2017

Copy link
Collaborator

emilio left a comment

Looks good, thanks!

@emilio

This comment has been minimized.

Copy link
Collaborator

emilio commented Nov 28, 2017

@bors-servo

This comment has been minimized.

Copy link
Contributor

bors-servo commented Nov 28, 2017

📌 Commit 89efc23 has been approved by emilio

@bors-servo

This comment has been minimized.

Copy link
Contributor

bors-servo commented Nov 28, 2017

⌛️ Testing commit 89efc23 with merge 75f9e1c...

bors-servo added a commit that referenced this pull request Nov 28, 2017

Auto merge of #1162 - tamird:enum-naming-consistency, r=emilio
Properly handle namespaces for enum configuration options

...by using canonical_path rather than canonical_name.

Fixes #1125.

r? @emilio
@bors-servo

This comment has been minimized.

Copy link
Contributor

bors-servo commented Nov 28, 2017

☀️ Test successful - status-travis
Approved by: emilio
Pushing 75f9e1c to master...

@bors-servo bors-servo merged commit 89efc23 into rust-lang:master Nov 28, 2017

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
homu Test successful
Details

@tamird tamird deleted the tamird:enum-naming-consistency branch Nov 28, 2017

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][]

This comment has been minimized.

@fitzgen

fitzgen Nov 28, 2017

Member

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.