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.10
Documenting route-recognizer v0.1.10
Running `rustdoc .cargo/registry/src/github.com-1ecc6299db9ec823/route-recognizer-0.1.10/src/lib.rs --crate-name route_recognizer -o /home/cratesfyi/route-recognizer-0.1.10/doc -L dependency=/home/cratesfyi/route-recognizer-0.1.10/debug -L dependency=/home/cratesfyi/route-recognizer-0.1.10/debug/deps`
.cargo/registry/src/github.com-1ecc6299db9ec823/route-recognizer-0.1.10/src/nfa.rs:235:35: 235:41 error: no method named `max_by` found for type `std::iter::Filter<std::vec::IntoIter<nfa::Thread>, [closure@.cargo/registry/src/github.com-1ecc6299db9ec823/route-recognizer-0.1.10/src/nfa.rs:231:55: 233:14 self:_]>` in the current scope
.cargo/registry/src/github.com-1ecc6299db9ec823/route-recognizer-0.1.10/src/nfa.rs:235 let thread = returned.max_by(|thread| ord(thread.state));
^~~~~~
error: Compilation failed, aborting rustdoc
thread 'main' panicked at 'ChainedError {
error: failed to compile `route-recognizer v0.1.10`, intermediate artifacts can be found at `/home/cratesfyi/route-recognizer-0.1.10`,
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.10/src/lib.rs --crate-name route_recognizer -o /home/cratesfyi/route-recognizer-0.1.10/doc -L dependency=/home/cratesfyi/route-recognizer-0.1.10/debug -L dependency=/home/cratesfyi/route-recognizer-0.1.10/debug/deps` (exit code: 101)
}
}', src/bin/cratesfyi.rs:119
note: Run with `RUST_BACKTRACE=1` for a backtrace.