Removed some warnings #158
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
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.
■First commit
Just remove the unnecessary semicolon.
■Second commit
The
into_iter()return the reference currently but this function will stop returning reference because of upcoming breaking change following issue so it won't be able to use*.Replacing with
iter(), it keeps returning reference.rust-lang/rust#66145
■Third commit
We can use
?operator instead oftry!.The RFC about this is following.
https://rust-lang.github.io/rfcs/1859-try-trait.html#desugaring-and-the-try-trait
■Fourth commit
The alloc crate is stable since Version 1.36.0 (2019-07-04) release so we don't have to require the attribute.