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 protobuf v0.0.10
Documenting protobuf v0.0.10
Running `rustdoc .cargo/registry/src/github.com-1ecc6299db9ec823/protobuf-0.0.10/src/lib/protobuf.rs --crate-name protobuf -o /home/cratesfyi/protobuf-0.0.10/doc -L dependency=/home/cratesfyi/protobuf-0.0.10/debug -L dependency=/home/cratesfyi/protobuf-0.0.10/debug/deps`
.cargo/registry/src/github.com-1ecc6299db9ec823/protobuf-0.0.10/src/lib/core.rs:138:55: 138:57 error: missing lifetime specifier [E0106]
.cargo/registry/src/github.com-1ecc6299db9ec823/protobuf-0.0.10/src/lib/core.rs:138 pub fn message_down_cast<M : Message>(m: &Message) -> &M {
^~
.cargo/registry/src/github.com-1ecc6299db9ec823/protobuf-0.0.10/src/lib/core.rs:138:55: 138:57 help: this function's return type contains a borrowed value, but the signature does not say which one of `m`'s 2 elided lifetimes it is borrowed from
error: Compilation failed, aborting rustdoc
thread 'main' panicked at 'ChainedError {
error: failed to compile `protobuf v0.0.10`, intermediate artifacts can be found at `/home/cratesfyi/protobuf-0.0.10`,
cause: ChainedError {
error: Could not document `protobuf`.,
cause: Process didn't exit successfully: `rustdoc .cargo/registry/src/github.com-1ecc6299db9ec823/protobuf-0.0.10/src/lib/protobuf.rs --crate-name protobuf -o /home/cratesfyi/protobuf-0.0.10/doc -L dependency=/home/cratesfyi/protobuf-0.0.10/debug -L dependency=/home/cratesfyi/protobuf-0.0.10/debug/deps` (exit code: 101)
}
}', src/bin/cratesfyi.rs:119
note: Run with `RUST_BACKTRACE=1` for a backtrace.