try_or_wrap 0.0.2

Macro for simplified handling of multiple error conditions in a single function. Like try!, but can aggregate more than one enum into a wrapper.
Build #23391 2016-08-17 04:11:17

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 try_or_wrap v0.0.2
Documenting try_or_wrap v0.0.2
Running `rustdoc .cargo/registry/src/github.com-1ecc6299db9ec823/try_or_wrap-0.0.2/src/lib.rs --crate-name try_or_wrap -o /home/cratesfyi/try_or_wrap-0.0.2/doc -L dependency=/home/cratesfyi/try_or_wrap-0.0.2/debug -L dependency=/home/cratesfyi/try_or_wrap-0.0.2/debug/deps`
.cargo/registry/src/github.com-1ecc6299db9ec823/try_or_wrap-0.0.2/src/lib.rs:28:1: 28:2 error: macros that expand to items must either be surrounded with braces or followed by a semicolon 
.cargo/registry/src/github.com-1ecc6299db9ec823/try_or_wrap-0.0.2/src/lib.rs:28 )
^
error: Compilation failed, aborting rustdoc 
thread 'main' panicked at 'ChainedError {
error: failed to compile `try_or_wrap v0.0.2`, intermediate artifacts can be found at `/home/cratesfyi/try_or_wrap-0.0.2`,
cause: ChainedError {
error: Could not document `try_or_wrap`.,
cause: Process didn't exit successfully: `rustdoc .cargo/registry/src/github.com-1ecc6299db9ec823/try_or_wrap-0.0.2/src/lib.rs --crate-name try_or_wrap -o /home/cratesfyi/try_or_wrap-0.0.2/doc -L dependency=/home/cratesfyi/try_or_wrap-0.0.2/debug -L dependency=/home/cratesfyi/try_or_wrap-0.0.2/debug/deps` (exit code: 101)
}
}', src/bin/cratesfyi.rs:119
note: Run with `RUST_BACKTRACE=1` for a backtrace.