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 enum-set v0.0.1 Documenting enum-set v0.0.1 Running `rustdoc .cargo/registry/src/github.com-1ecc6299db9ec823/enum-set-0.0.1/src/lib.rs --crate-name enum_set -o /home/cratesfyi/enum-set-0.0.1/doc -L dependency=/home/cratesfyi/enum-set-0.0.1/debug -L dependency=/home/cratesfyi/enum-set-0.0.1/debug/deps` .cargo/registry/src/github.com-1ecc6299db9ec823/enum-set-0.0.1/src/lib.rs:26:5: 26:18 error: unresolved import `std::num::Int`. There is no `Int` in `std::num` [E0432] .cargo/registry/src/github.com-1ecc6299db9ec823/enum-set-0.0.1/src/lib.rs:26 use std::num::Int; ^~~~~~~~~~~~~ .cargo/registry/src/github.com-1ecc6299db9ec823/enum-set-0.0.1/src/lib.rs:95:21: 95:30 error: no associated item named `BITS` found for type `u32` in the current scope .cargo/registry/src/github.com-1ecc6299db9ec823/enum-set-0.0.1/src/lib.rs:95 assert!(value < u32::BITS as u32, ^~~~~~~~~ .cargo/registry/src/github.com-1ecc6299db9ec823/enum-set-0.0.1/src/lib.rs:95:5: 96:72 note: in this expansion of assert! (defined in <std macros>) .cargo/registry/src/github.com-1ecc6299db9ec823/enum-set-0.0.1/src/lib.rs:96:57: 96:66 error: no associated item named `BITS` found for type `u32` in the current scope .cargo/registry/src/github.com-1ecc6299db9ec823/enum-set-0.0.1/src/lib.rs:96 "EnumSet only supports up to {} variants.", u32::BITS - 1); ^~~~~~~~~ <std macros>:9:3: 9:42 note: in this expansion of format_args! <std macros>:5:15: 5:40 note: in this expansion of panic! (defined in <std macros>) .cargo/registry/src/github.com-1ecc6299db9ec823/enum-set-0.0.1/src/lib.rs:95:5: 96:72 note: in this expansion of assert! (defined in <std macros>) error: Compilation failed, aborting rustdoc thread 'main' panicked at 'ChainedError { error: failed to compile `enum-set v0.0.1`, intermediate artifacts can be found at `/home/cratesfyi/enum-set-0.0.1`, cause: ChainedError { error: Could not document `enum-set`., cause: Process didn't exit successfully: `rustdoc .cargo/registry/src/github.com-1ecc6299db9ec823/enum-set-0.0.1/src/lib.rs --crate-name enum_set -o /home/cratesfyi/enum-set-0.0.1/doc -L dependency=/home/cratesfyi/enum-set-0.0.1/debug -L dependency=/home/cratesfyi/enum-set-0.0.1/debug/deps` (exit code: 101) } }', src/bin/cratesfyi.rs:119 note: Run with `RUST_BACKTRACE=1` for a backtrace.