Skip to content
This repository has been archived by the owner on Feb 1, 2019. It is now read-only.

remove lint unused_doc_comment #86

Open
timxor opened this issue May 28, 2018 · 3 comments
Open

remove lint unused_doc_comment #86

timxor opened this issue May 28, 2018 · 3 comments

Comments

@timxor
Copy link
Contributor

timxor commented May 28, 2018

To Reproduce
Steps to reproduce the behavior:

1. cargo make all

Describe the bug

warning: lint unused_doc_comment has been renamed to unused_doc_comments
  --> env/src/lib.rs:11:5
   |
11 |     error_chain!{}
   |     ^^^^^^^^^^^^^^
   |
   = note: #[warn(renamed_and_removed_lints)] on by default
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
  --> env/src/lib.rs:11:5
   |
11 |     error_chain!{}
   |     ^^^^^^^^^^^^^^
   |
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
  --> env/src/lib.rs:11:5
   |
11 |     error_chain!{}
   |     ^^^^^^^^^^^^^^
   |
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
  --> env/src/lib.rs:11:5
   |
11 |     error_chain!{}
   |     ^^^^^^^^^^^^^^
   |
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

   Compiling syntex_syntax v0.58.1
   Compiling env_logger v0.5.10
   Compiling ethereum-types-serialize v0.2.1
   Compiling chrono v0.4.2
   Compiling ethbloom v0.5.0
   Compiling diamond-drops-cli v0.1.0-a (file:///Users/tim.siwula/Desktop/diamond_drops/cli)
warning: lint unused_doc_comment has been renamed to unused_doc_comments
  --> cli/src/lib.rs:16:5
   |
16 |     error_chain! { }
   |     ^^^^^^^^^^^^^^^^
   |
   = note: #[warn(renamed_and_removed_lints)] on by default
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
  --> cli/src/lib.rs:16:5
   |
16 |     error_chain! { }
   |     ^^^^^^^^^^^^^^^^
   |
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
  --> cli/src/lib.rs:16:5
   |
16 |     error_chain! { }
   |     ^^^^^^^^^^^^^^^^
   |
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
  --> cli/src/lib.rs:16:5
   |
16 |     error_chain! { }
   |     ^^^^^^^^^^^^^^^^
   |
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
 --> cli/src/modules/mod.rs:7:5
  |
7 |     error_chain! { }
  |     ^^^^^^^^^^^^^^^^
  |
  = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
 --> cli/src/modules/mod.rs:7:5
  |
7 |     error_chain! { }
  |     ^^^^^^^^^^^^^^^^
  |
  = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
 --> cli/src/modules/mod.rs:7:5
  |
7 |     error_chain! { }
  |     ^^^^^^^^^^^^^^^^
  |
  = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
 --> cli/src/modules/mod.rs:7:5
  |
7 |     error_chain! { }
  |     ^^^^^^^^^^^^^^^^
  |
  = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

   Compiling mml v0.1.41
   Compiling diamond-drops-node v0.1.0-a (file:///Users/tim.siwula/Desktop/diamond_drops/node)
warning: lint unused_doc_comment has been renamed to unused_doc_comments
 --> node/src/modules/errors.rs:1:1
  |
1 | error_chain!{}
  | ^^^^^^^^^^^^^^
  |
  = note: #[warn(renamed_and_removed_lints)] on by default
  = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
 --> node/src/modules/errors.rs:1:1
  |
1 | error_chain!{}
  | ^^^^^^^^^^^^^^
  |
  = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
 --> node/src/modules/errors.rs:1:1
  |
1 | error_chain!{}
  | ^^^^^^^^^^^^^^
  |
  = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
 --> node/src/modules/errors.rs:1:1
  |
1 | error_chain!{}
  | ^^^^^^^^^^^^^^
........
@jamesray1
Copy link
Member

Hmm, this looks like an issue with the error-chain crate. Will cross post this there. rust-lang-deprecated/error-chain#245

@jamesray1
Copy link
Member

So we can add to #90 in all crates at the top of lib.rs an #[allow!(renamed_and_removed_lints)] and leave a comment with a link to this issue until a better solution is found.

@jamesray1
Copy link
Member

Referencing #90 (comment).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants