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 parse-regex v0.0.1
Documenting parse-regex v0.0.1
Running `rustdoc .cargo/registry/src/github.com-1ecc6299db9ec823/parse-regex-0.0.1/src/lib.rs --crate-name parse_regex -o /home/cratesfyi/parse-regex-0.0.1/doc -L dependency=/home/cratesfyi/parse-regex-0.0.1/debug -L dependency=/home/cratesfyi/parse-regex-0.0.1/debug/deps`
.cargo/registry/src/github.com-1ecc6299db9ec823/parse-regex-0.0.1/src/parser.rs:68:16: 68:23 error: no method named `char_at` found for type `std::string::String` in the current scope
.cargo/registry/src/github.com-1ecc6299db9ec823/parse-regex-0.0.1/src/parser.rs:68 self.s.char_at(self.pos)
^~~~~~~
error: Compilation failed, aborting rustdoc
thread 'main' panicked at 'ChainedError {
error: failed to compile `parse-regex v0.0.1`, intermediate artifacts can be found at `/home/cratesfyi/parse-regex-0.0.1`,
cause: ChainedError {
error: Could not document `parse-regex`.,
cause: Process didn't exit successfully: `rustdoc .cargo/registry/src/github.com-1ecc6299db9ec823/parse-regex-0.0.1/src/lib.rs --crate-name parse_regex -o /home/cratesfyi/parse-regex-0.0.1/doc -L dependency=/home/cratesfyi/parse-regex-0.0.1/debug -L dependency=/home/cratesfyi/parse-regex-0.0.1/debug/deps` (exit code: 101)
}
}', src/bin/cratesfyi.rs:119
note: Run with `RUST_BACKTRACE=1` for a backtrace.