Build failed. If you want to re-trigger a documentation build, you can do it here. You can find more information on docs.rs builds documentation on the builds page.
# rustc version rustc 1.12.0-nightly (54c0dcfd6 2016-07-28)
# docs.rs version cratesfyi 0.2.0 (5dbd676 2016-07-30)
# build log Updating registry `https://github.com/rust-lang/crates.io-index` Downloading type_printer v0.0.1 Documenting type_printer v0.0.1 Running `rustdoc .cargo/registry/src/github.com-1ecc6299db9ec823/type_printer-0.0.1/src/lib.rs --crate-name type_printer -o /home/cratesfyi/type_printer-0.0.1/doc -L dependency=/home/cratesfyi/type_printer-0.0.1/debug -L dependency=/home/cratesfyi/type_printer-0.0.1/debug/deps` .cargo/registry/src/github.com-1ecc6299db9ec823/type_printer-0.0.1/src/lib.rs:6:13: 6:44 error: use of unstable library feature 'core_intrinsics': intrinsics are unlikely to ever be stabilized, instead they should be used through stabilized interfaces in the rest of the standard library (see issue #0) .cargo/registry/src/github.com-1ecc6299db9ec823/type_printer-0.0.1/src/lib.rs:6 std::intrinsics::type_name::<T>() ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .cargo/registry/src/github.com-1ecc6299db9ec823/type_printer-0.0.1/src/lib.rs:6:13: 6:44 help: add #![feature(core_intrinsics)] to the crate attributes to enable error: Compilation failed, aborting rustdoc thread 'main' panicked at 'ChainedError { error: failed to compile `type_printer v0.0.1`, intermediate artifacts can be found at `/home/cratesfyi/type_printer-0.0.1`, cause: ChainedError { error: Could not document `type_printer`., cause: Process didn't exit successfully: `rustdoc .cargo/registry/src/github.com-1ecc6299db9ec823/type_printer-0.0.1/src/lib.rs --crate-name type_printer -o /home/cratesfyi/type_printer-0.0.1/doc -L dependency=/home/cratesfyi/type_printer-0.0.1/debug -L dependency=/home/cratesfyi/type_printer-0.0.1/debug/deps` (exit code: 101) } }', src/bin/cratesfyi.rs:119 note: Run with `RUST_BACKTRACE=1` for a backtrace.