Update to 2018 edition and fix warnings #56
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Manishearth
approved these changes
Apr 6, 2021
|
@bors r+ |
|
@bors-servo r=Manishearth |
|
📌 Commit d01aa65 has been approved by |
|
☀️ Test successful - checks-travis |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This increases the minimum supported Rust version from 1.17 to 1.31 (released in December 2018). I hope this will have little impact on users, since this version of Rust is almost 2.5 years old, and because our main downstream crates (
urlandpostgres-protocol) already require 1.31 or later.Many of the changes below are fixing new rustc/clippy warnings added in recent toolchains.
r? @Manishearth