I’m looking for a way to deny rustdoc warnings in my own code, but allow them in upstream crates.
It’s easy to do this for compiler warnings. This will not break the build if I use a Rust 2015 crate:
But that does not seem to hold for rustdoc warnings. Doing this:
breaks our build due to upstream errors in
error: `[impls::next_u32_via_fill]` cannot be resolved, ignoring it... --> ~\.cargo\registry\src\github.com-1ecc6299db9ec823\rand_core-0.4.0\src\lib.rs:144:24 | 144 | /// [`fill_bytes`][impls::next_u32_via_fill]. | ^^^^^^^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring | = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Is there some way I can enforce correctness in code I’ve written, without getting blocked by upstream errors?