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 iobuf v3.5.3
Documenting iobuf v3.5.3
Running `rustdoc .cargo/registry/src/github.com-1ecc6299db9ec823/iobuf-3.5.3/src/lib.rs --crate-name iobuf -o /home/cratesfyi/iobuf-3.5.3/doc -L dependency=/home/cratesfyi/iobuf-3.5.3/debug -L dependency=/home/cratesfyi/iobuf-3.5.3/debug/deps`
.cargo/registry/src/github.com-1ecc6299db9ec823/iobuf-3.5.3/src/raw.rs:5:20: 5:23 error: expected identifier, found keyword `mod`
.cargo/registry/src/github.com-1ecc6299db9ec823/iobuf-3.5.3/src/raw.rs:5 use core::atomic::{mod, AtomicUint};
^~~
.cargo/registry/src/github.com-1ecc6299db9ec823/iobuf-3.5.3/src/raw.rs:6:17: 6:20 error: expected identifier, found keyword `mod`
.cargo/registry/src/github.com-1ecc6299db9ec823/iobuf-3.5.3/src/raw.rs:6 use core::fmt::{mod, Formatter};
^~~
error: aborting due to previous error
thread 'main' panicked at 'ChainedError {
error: failed to compile `iobuf v3.5.3`, intermediate artifacts can be found at `/home/cratesfyi/iobuf-3.5.3`,
cause: ChainedError {
error: Could not document `iobuf`.,
cause: Process didn't exit successfully: `rustdoc .cargo/registry/src/github.com-1ecc6299db9ec823/iobuf-3.5.3/src/lib.rs --crate-name iobuf -o /home/cratesfyi/iobuf-3.5.3/doc -L dependency=/home/cratesfyi/iobuf-3.5.3/debug -L dependency=/home/cratesfyi/iobuf-3.5.3/debug/deps` (exit code: 101)
}
}', src/bin/cratesfyi.rs:119
note: Run with `RUST_BACKTRACE=1` for a backtrace.