Skip to content

Code cleanup in check_match.rs #37243

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
wants to merge 4 commits into from

Conversation

jfirebaugh
Copy link
Contributor

@jfirebaugh jfirebaugh commented Oct 18, 2016

Best reviewed ignoring whitespace changes.

See commits for individual changes.

Based on the commit comment for 5af5f26, I believe the exports were used by old trans and became unused with #35764.

@rust-highfive
Copy link
Contributor

r? @Aatch

(rust_highfive has picked a reviewer for you, use r? to override)

@jfirebaugh
Copy link
Contributor Author

Pinging @arielb1 per @eddyb on IRC -- I understand if there's a reluctance for pure "cleanup" PRs due to the potential for causing merge conflicts.

@eddyb
Copy link
Member

eddyb commented Oct 18, 2016

The conflict in question is with #36695 - if you two can agree on a way to handle this, it'd be great.

@jfirebaugh
Copy link
Contributor Author

Thanks for the pointer @eddyb. @arielb1, I'm happy to wait for #36695 to land -- some or all of these changes may well be unnecessary after that. Let me know.

@bors
Copy link
Collaborator

bors commented Oct 27, 2016

☔ The latest upstream changes (presumably #36695) made this pull request unmergeable. Please resolve the merge conflicts.

@alexcrichton
Copy link
Member

Closing due to inactivity, but feel free to resubmit with a rebase!

@jfirebaugh jfirebaugh deleted the check_match-cleanup branch November 13, 2016 22:05
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants