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

Fix following removal of Attribute.value #136

Merged
merged 1 commit into from
Mar 21, 2017

Conversation

jonhoo
Copy link
Contributor

@jonhoo jonhoo commented Mar 20, 2017

Since rust-lang/rust#40346 has now been merged, syntax::Attribute no longer has a .value field. Instead, we must follow the token stream and modify the tokens directly. For Docstring attributes, there should only be one token, the docstring value.

Fixes #137

@tikue
Copy link
Collaborator

tikue commented Mar 20, 2017

Can you confirm this works? You can check the FutureService trait's associated types' doc strings -- there shouldn't be any {}. It should look like The type of future returned by rpc.

@jonhoo jonhoo force-pushed the fix-for-rust-40346-merge branch 2 times, most recently from f0c9aa3 to 8ecaf40 Compare March 21, 2017 17:42
Copy link
Collaborator

@tikue tikue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

Since rust-lang/rust#40346 has now been merged, Attribute no longer has
a .value field. Instead, we must follow the token stream and modify the
tokens directly. For Docstring attributes, there should only be one
token, the docstring value.
@jonhoo jonhoo force-pushed the fix-for-rust-40346-merge branch from 8ecaf40 to d578510 Compare March 21, 2017 17:44
@tikue tikue self-assigned this Mar 21, 2017
@tikue tikue merged commit c8be9b6 into google:master Mar 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants