rustdoc panics if target crate has compilation errors

[japaric]

Updated issue

STR

// err.rs
fn main() { 0 }

Output

$ rustc err.rs 2>/dev/null || echo compilation error as expected
compilation error as expected
$ rustdoc err.rs
err.rs:2:5: 2:6 error: mismatched types: expected `()`, found `_` (expected (), found integral variable)
err.rs:2     0
             ^
error: aborting due to previous error
task '<unnamed>' panicked at 'Box<Any>', /var/tmp/paludis/build/dev-lang-rust-scm/work/rust-scm/src/libsyntax/diagnostic.rs:142
task '<main>' panicked at 'called `Result::unwrap()` on an `Err` value: rustc failed', /var/tmp/paludis/build/dev-lang-rust-scm/work/rust-scm/src/libcore/result.rs:743

---

Original issue: rustdoc panics with #![deny(missing_docs] and associated items

STR

#![deny(missing_docs)]
#![feature(associated_types)]

//! Crate

/// Trait
pub trait AsSlice {
    /// Item
    type Item;

    // Forgot to document the method
    fn as_slice(&self) -> &[<Self as AsSlice>::Item];
}

Output

ai.rs:12:5: 12:53 error: missing documentation for a type method
ai.rs:12     fn as_slice(&self) -> &[<Self as AsSlice>::Item];
             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ai.rs:1:9: 1:21 note: lint level defined here
ai.rs:1 #![deny(missing_docs)]
                ^~~~~~~~~~~~
error: aborting due to previous error
task '<unnamed>' panicked at 'Box<Any>', /var/tmp/paludis/build/dev-lang-rust-scm/work/rust-scm/src/libsyntax/diagnostic.rs:142
task '<main>' panicked at 'called `Result::unwrap()` on an `Err` value: rustc failed', /var/tmp/paludis/build/dev-lang-rust-scm/work/rust-scm/src/libcore/result.rs:743

Version

#19174 on top of c9f6d69

cc @tomjakubowski

[tomjakubowski]

This is a more general problem with rustdoc; it panics on any compilation error.

[japaric]

@tomjakubowski Ah yes, you are right, I've seen that before. Do you know if there's a tracking issue for that (rustdoc panics on any compilation error)?

[tomjakubowski]

@japaric I don't think there is a more general issue for this, might be reasonable to repurpose this issue :)

[japaric]

@tomjakubowski Done!

[tamird]

@steveklabnik I think this should not be tagged I-ICE since it is strictly a rustdoc issue.

[bltavares]

Triaging this issue.

It still happens on rustc 1.7.0-nightly (b4707ebca 2015-12-27)

[mitaa]

The two testcases don't panic for me (fixed/needstest ?)

rustdoc 1.8.0-nightly (57c357d89 2016-02-16)