session: disable internal lints for rustdoc
If an internal lint uses `typeck_results` or similar queries then that can result in rustdoc checking code that it shouldn't (e.g. from other platforms) and emit compilation errors. Signed-off-by: David Wood <david.wood@huawei.com>
This commit is contained in:
parent
1b8e4b9391
commit
f5e005f0ca
5 changed files with 11 additions and 17 deletions
|
@ -51,20 +51,6 @@ fn typeck_results_of_method_fn<'tcx>(
|
|||
cx: &LateContext<'tcx>,
|
||||
expr: &Expr<'_>,
|
||||
) -> Option<(Span, DefId, ty::subst::SubstsRef<'tcx>)> {
|
||||
// FIXME(rustdoc): Lints which use this function use typecheck results which can cause
|
||||
// `rustdoc` to error if there are resolution failures.
|
||||
//
|
||||
// As internal lints are currently always run if there are `unstable_options`, they are added
|
||||
// to the lint store of rustdoc. Internal lints are also not used via the `lint_mod` query.
|
||||
// Crate lints run outside of a query so rustdoc currently doesn't disable them.
|
||||
//
|
||||
// Instead of relying on this, either change crate lints to a query disabled by rustdoc, only
|
||||
// run internal lints if the user is explicitly opting in or figure out a different way to
|
||||
// avoid running lints for rustdoc.
|
||||
if cx.tcx.sess.opts.actually_rustdoc {
|
||||
return None;
|
||||
}
|
||||
|
||||
match expr.kind {
|
||||
ExprKind::MethodCall(segment, _, _)
|
||||
if let Some(def_id) = cx.typeck_results().type_dependent_def_id(expr.hir_id) =>
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue