Skip to content

Don't perform span mangling when building field/tup access nodes #38194

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

Merged
merged 1 commit into from
Dec 19, 2016

Conversation

sgrif
Copy link
Contributor

@sgrif sgrif commented Dec 6, 2016

There are no guarantees that the two spans used to create the new one
come from the same place or are even valid.

Fixes #36081.

There are no guarantees that the two spans used to create the new one
come from the same place or are even valid.

Fixes rust-lang#36081.
@rust-highfive
Copy link
Contributor

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nrc (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

@nrc
Copy link
Member

nrc commented Dec 18, 2016

@bors: r+

@bors
Copy link
Collaborator

bors commented Dec 18, 2016

📌 Commit 0ddf618 has been approved by nrc

@bors
Copy link
Collaborator

bors commented Dec 19, 2016

⌛ Testing commit 0ddf618 with merge cc662ef...

bors added a commit that referenced this pull request Dec 19, 2016
Don't perform span mangling when building field/tup access nodes

There are no guarantees that the two spans used to create the new one
come from the same place or are even valid.

Fixes #36081.
@bors bors merged commit 0ddf618 into rust-lang:master Dec 19, 2016
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.

4 participants