Deep dead_code warning is annoying

[comex]

Currently, any code which is not reachable is considered dead and warned about, even if there are references to it from other dead code. Thus if I implement a tree of functions/methods which call each other, but haven't yet implemented any code to actually call into it yet, every single function in the family will produce a dead code warning, not only the root functions that actually lack any textual references. This is annoyingly verbose.

As a comparison, Clang and GCC only produce warnings for the roots in the equivalent situation for C code.

[thestinger]

I find it very useful. It frequently finds graphs of genuinely dead code that either indicates a bug or allows for removing a bunch of obsolete code. In my opinion, the entire point of having this stuff as warnings instead of errors is so that it doesn't get in the way of development.

[sanxiyn]

This is by design. I note that if you add #[allow(dead_code)] to the root, warnings are silenced for the entire tree. You do not need to add allow attributes to all of them.

[steveklabnik]

At this point, I believe a change to a lint like this would need an RFC. As @sanxiyn notes, this is intended behavior currently.