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 route-recognizer v0.1.9
Documenting route-recognizer v0.1.9
Running `rustdoc .cargo/registry/src/github.com-1ecc6299db9ec823/route-recognizer-0.1.9/src/lib.rs --crate-name route_recognizer -o /home/cratesfyi/route-recognizer-0.1.9/doc -L dependency=/home/cratesfyi/route-recognizer-0.1.9/debug -L dependency=/home/cratesfyi/route-recognizer-0.1.9/debug/deps`
.cargo/registry/src/github.com-1ecc6299db9ec823/route-recognizer-0.1.9/src/lib.rs:59:28: 59:32 error: `#[derive]` for custom traits is not stable enough for use and is subject to change (see issue #29644)
.cargo/registry/src/github.com-1ecc6299db9ec823/route-recognizer-0.1.9/src/lib.rs:59 #[derive(PartialEq, Clone, Show)]
^~~~
.cargo/registry/src/github.com-1ecc6299db9ec823/route-recognizer-0.1.9/src/lib.rs:59:28: 59:32 help: add #![feature(custom_derive)] to the crate attributes to enable
error: aborting due to previous error
thread 'main' panicked at 'ChainedError {
error: failed to compile `route-recognizer v0.1.9`, intermediate artifacts can be found at `/home/cratesfyi/route-recognizer-0.1.9`,
cause: ChainedError {
error: Could not document `route-recognizer`.,
cause: Process didn't exit successfully: `rustdoc .cargo/registry/src/github.com-1ecc6299db9ec823/route-recognizer-0.1.9/src/lib.rs --crate-name route_recognizer -o /home/cratesfyi/route-recognizer-0.1.9/doc -L dependency=/home/cratesfyi/route-recognizer-0.1.9/debug -L dependency=/home/cratesfyi/route-recognizer-0.1.9/debug/deps` (exit code: 101)
}
}', src/bin/cratesfyi.rs:119
note: Run with `RUST_BACKTRACE=1` for a backtrace.