False doc_markdown warnings

[compressed]

When I use cfg_attr for conditional examples in doc comments like this:

#![cfg_attr(feature = "a", doc = " ```")]
#![cfg_attr(not(feature = "a"), doc = " ```ignore")]
//! fn main() {
//!     let s = "localhost:10000".to_string();
//!     println!("{}", s);
//! }
//! ```

I receive false warnings:

cargo clippy --features a
...
warning: you should put `to_string` between ticks in the documentation, #[warn(doc_markdown)] on by default
  --> src/lib.rs:66:35
   |
66 | //!     let s = "localhost:10000".to_string();
   |                                   ^^^^^^^^^

[oli-obk]

I wasn't even aware that's possible. That's amazing...

[compressed]

Yeah, I had to learn about how to do it correctly in the first place 😄. Definitely an edge case.

[mcarton]

This is such a hack, I hesitate between 😄 and 😱.

[Manishearth]

I think this is a niche enough use case that clippy shouldn't attempt to handle it. idk. Ultimately, the way clippy is supposed to be used is with a liberal sprinkling of allows.

[compressed]

I'd be fine putting an allow, but since it's at the crate/module level, I'm not sure how to just have it apply there.

If I put #![cfg_attr(feature = "cargo-clippy", allow(doc_markdown))], I'd turn off the validation for the entire crate, not just this section. Maybe there is a better workaround?

Edit: Actually for my use case it's at the crate level so I that's where I'm stuck. If it was just a module I could apply a #[cfg_attr(feature = "cargo-clippy", allow(doc_markdown))] to that mod specifically.

[iliekturtles]

I ran into the same issue at the crate level and I'm hesitant to add #![allow(doc_markdown)]. I briefly attempted to do a github-wide search for other repositories to see how many others use this same functionality, but didn't get very far.