This repository has been archived by the owner on Aug 16, 2021. It is now read-only.
Fix new renamed_and_removed_lints warning #247
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
I've verified that this now produces no warnings with Rust 1.26.1 and 1.28.0-nightly (c3b09c968 2018-05-27)
|
Getting rid of these warnings would be very much appreciated. |
|
Thanks @Yamakaky
On Jun 16, 2018 4:59 AM, "Yamakaky" <notifications@github.com> wrote:
Merged #247 <#247>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#247 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAI_DjlFWXv1ig-qlQHl6eTMvdm90iFCks5t9PMygaJpZM4UWxT4>
.
|
|
Would be amazing to get a release out with this, perhaps a backport and a tiny release on 0.11 too? :) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Builds on @hoodie's work in #246 to allow both
unused_doc_commentandunused_doc_commentsin a fully back-compatible fashion.Fixes #245