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
Build failed, waiting for other jobs to finish...
Updating registry `https://github.com/rust-lang/crates.io-index`
Compiling winapi-build v0.1.1
Running `rustc .cargo/registry/src/github.com-1ecc6299db9ec823/winapi-build-0.1.1/src/lib.rs --crate-name build --crate-type lib -g -C metadata=493a7b0628804707 -C extra-filename=-493a7b0628804707 --out-dir /home/cratesfyi/pistoncore-event_loop-0.0.0/debug/deps --emit=dep-info,link -L dependency=/home/cratesfyi/pistoncore-event_loop-0.0.0/debug/deps -L dependency=/home/cratesfyi/pistoncore-event_loop-0.0.0/debug/deps --cap-lints allow`
Compiling pistoncore-current v0.0.0
Running `rustc .cargo/registry/src/github.com-1ecc6299db9ec823/pistoncore-current-0.0.0/src/lib.rs --crate-name current --crate-type lib -g -C metadata=fd6b6392b73c0ccc -C extra-filename=-fd6b6392b73c0ccc --out-dir /home/cratesfyi/pistoncore-event_loop-0.0.0/debug/deps --emit=dep-info,link -L dependency=/home/cratesfyi/pistoncore-event_loop-0.0.0/debug/deps -L dependency=/home/cratesfyi/pistoncore-event_loop-0.0.0/debug/deps --cap-lints allow`
Compiling libc v0.2.15
Running `rustc .cargo/registry/src/github.com-1ecc6299db9ec823/libc-0.2.15/src/lib.rs --crate-name libc --crate-type lib -g --cfg feature=\"use_std\" --cfg feature=\"default\" -C metadata=1bd8847afb79f283 -C extra-filename=-1bd8847afb79f283 --out-dir /home/cratesfyi/pistoncore-event_loop-0.0.0/debug/deps --emit=dep-info,link -L dependency=/home/cratesfyi/pistoncore-event_loop-0.0.0/debug/deps -L dependency=/home/cratesfyi/pistoncore-event_loop-0.0.0/debug/deps --cap-lints allow`
Compiling winapi v0.2.8
Running `rustc .cargo/registry/src/github.com-1ecc6299db9ec823/winapi-0.2.8/src/lib.rs --crate-name winapi --crate-type lib -g -C metadata=0889532d327ff4e2 -C extra-filename=-0889532d327ff4e2 --out-dir /home/cratesfyi/pistoncore-event_loop-0.0.0/debug/deps --emit=dep-info,link -L dependency=/home/cratesfyi/pistoncore-event_loop-0.0.0/debug/deps -L dependency=/home/cratesfyi/pistoncore-event_loop-0.0.0/debug/deps --cap-lints allow`
.cargo/registry/src/github.com-1ecc6299db9ec823/pistoncore-current-0.0.0/src/current.rs:8:35: 8:36 error: macros that expand to items must either be surrounded with braces or followed by a semicolon
.cargo/registry/src/github.com-1ecc6299db9ec823/pistoncore-current-0.0.0/src/current.rs:8 = RefCell::new(HashMap::new()))
^
.cargo/registry/src/github.com-1ecc6299db9ec823/pistoncore-current-0.0.0/src/current.rs:34:1: 34:21 error: The attribute `unsafe_destructor` is currently unknown to the compiler and may have meaning added to it in the future (see issue #29642)
.cargo/registry/src/github.com-1ecc6299db9ec823/pistoncore-current-0.0.0/src/current.rs:34 #[unsafe_destructor]
^~~~~~~~~~~~~~~~~~~~
.cargo/registry/src/github.com-1ecc6299db9ec823/pistoncore-current-0.0.0/src/current.rs:34:1: 34:21 help: add #![feature(custom_attribute)] to the crate attributes to enable
error: aborting due to previous error
thread 'main' panicked at 'ChainedError {
error: failed to compile `pistoncore-event_loop v0.0.0`, intermediate artifacts can be found at `/home/cratesfyi/pistoncore-event_loop-0.0.0`,
cause: ChainedError {
error: Could not compile `pistoncore-current`.,
cause: Process didn't exit successfully: `rustc .cargo/registry/src/github.com-1ecc6299db9ec823/pistoncore-current-0.0.0/src/lib.rs --crate-name current --crate-type lib -g -C metadata=fd6b6392b73c0ccc -C extra-filename=-fd6b6392b73c0ccc --out-dir /home/cratesfyi/pistoncore-event_loop-0.0.0/debug/deps --emit=dep-info,link -L dependency=/home/cratesfyi/pistoncore-event_loop-0.0.0/debug/deps -L dependency=/home/cratesfyi/pistoncore-event_loop-0.0.0/debug/deps --cap-lints allow` (exit code: 101)
}
}', src/bin/cratesfyi.rs:119
note: Run with `RUST_BACKTRACE=1` for a backtrace.