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.26.0-dev (5c1d29af0 2018-03-03)
# docs.rs version cratesfyi 0.5.0 (579f83b 2018-03-05)
# build log Updating registry `https://github.com/rust-lang/crates.io-index` Downloading pidfile v0.1.0 Fresh libc v0.2.39 Fresh byteorder v1.2.1 Fresh cfg-if v0.1.2 Fresh bitflags v1.0.1 Fresh void v1.0.2 Fresh iovec v0.1.2 Fresh bytes v0.4.6 Fresh nix v0.10.0 Documenting pidfile v0.1.0 Running `rustdoc --crate-name pidfile .cargo/registry/src/github.com-1ecc6299db9ec823/pidfile-0.1.0/src/lib.rs -o /home/cratesfyi/cratesfyi/doc -Z unstable-options --resource-suffix -20180303-1.26.0-dev-5c1d29af0 -L dependency=/home/cratesfyi/cratesfyi/debug/deps --extern nix=/home/cratesfyi/cratesfyi/debug/deps/libnix-4b10a7edd88e65c9.rlib --extern-version nix=nix,0.10.0` error: macros that expand to items must either be surrounded with braces or followed by a semicolon --> .cargo/registry/src/github.com-1ecc6299db9ec823/pidfile-0.1.0/src/file_posix.rs:22:19 | 22 | macro_rules! check( | ___________________^ 23 | | ($expr:expr) => ({ 24 | | let mut ret; 25 | | ... | 46 | | }) 47 | | ) | |_^ error: aborting due to previous error thread 'main' panicked at 'Error( CargoError( ChainedError { error: Could not document `pidfile`., cause: process didn't exit successfully: `rustdoc --crate-name pidfile .cargo/registry/src/github.com-1ecc6299db9ec823/pidfile-0.1.0/src/lib.rs -o /home/cratesfyi/cratesfyi/doc -Z unstable-options --resource-suffix -20180303-1.26.0-dev-5c1d29af0 -L dependency=/home/cratesfyi/cratesfyi/debug/deps --extern nix=/home/cratesfyi/cratesfyi/debug/deps/libnix-4b10a7edd88e65c9.rlib --extern-version nix=nix,0.10.0` (exit code: 101) } ), State { next_error: None, backtrace: None } )', src/bin/cratesfyi.rs:142:13 note: Run with `RUST_BACKTRACE=1` for a backtrace.