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.
# error kind ExecutionFailed
# pre-build errors command failed: exit status: 101
# rustc version rustc 1.98.0-nightly (d1fc603d1 2026-05-26)
# docs.rs version docsrs 0.0.0 (f16e33f3e6ac9fc9e4413728c5dd1b2ba1c6b799 2026-05-23 )
# build log [INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "DOCS_RS=1" "-w" "/opt/rustwide/workdir" "--user" "1001:1001" "cc64f254db457c557118cd91f4cae619152afa675c989ae266c20f6bb500ce84" "/opt/rustwide/cargo-home/bin/cargo" "+nightly" "rustdoc" "--lib" "-Zrustdoc-map" "--config" "build.rustdocflags=[\"--cfg\", \"docsrs\", \"-Z\", \"unstable-options\", \"--emit=invocation-specific\", \"--resource-suffix\", \"-20260526-1.98.0-nightly-d1fc603d1\", \"--static-root-path\", \"/-/rustdoc.static/\", \"--cap-lints\", \"warn\", \"--extern-html-root-takes-precedence\"]" "--offline" "-Zunstable-options" "--config=doc.extern-map.registries.crates-io=\"https://docs.rs/{pkg_name}/{version}/x86_64-unknown-linux-gnu\"" "-Zrustdoc-scrape-examples" "-j6" "--target" "x86_64-unknown-linux-gnu", kill_on_drop: false }` [INFO] [stderr] warning: target filter specified, but no targets matched; this is a no-op [INFO] [stderr] Documenting array-matrix v0.1.4 (/opt/rustwide/workdir) [INFO] [stderr] warning: the feature `generic_const_exprs` is incomplete and may not be safe to use and/or cause compiler crashes [INFO] [stderr] --> src/lib.rs:1:12 [INFO] [stderr] | [INFO] [stderr] 1 | #![feature(generic_const_exprs)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #76560 <https://github.com/rust-lang/rust/issues/76560> for more information [INFO] [stderr] = note: `#[warn(incomplete_features)]` on by default [INFO] [stderr] [INFO] [stderr] error[E0119]: conflicting implementations of trait `matrix::submatrix::Submatrix<[[_; _]; _]>` for type `[[_; _]; _]` [INFO] [stderr] --> src/matrix/submatrix.rs:49:1 [INFO] [stderr] | [INFO] [stderr] 36 | / impl<F: Clone, const L: usize, const H: usize> Submatrix<[[F; L - 1]; H]> for [[F; L]; H] [INFO] [stderr] 37 | | where [INFO] [stderr] 38 | | Self: Matrix, [INFO] [stderr] 39 | | [[F; L - 1]; H]: Matrix [INFO] [stderr] | |___________________________- first implementation here [INFO] [stderr] ... [INFO] [stderr] 49 | / impl<F: Clone, const L: usize, const H: usize> Submatrix<[[F; L]; H - 1]> for [[F; L]; H] [INFO] [stderr] 50 | | where [INFO] [stderr] 51 | | Self: Matrix, [INFO] [stderr] 52 | | [[F; L]; H - 1]: Matrix [INFO] [stderr] | |___________________________^ conflicting implementation for `[[_; _]; _]` [INFO] [stderr] [INFO] [stderr] error[E0119]: conflicting implementations of trait `matrix::submatrix::Submatrix<[[_; _]; _]>` for type `[[_; _]; _]` [INFO] [stderr] --> src/matrix/submatrix.rs:62:1 [INFO] [stderr] | [INFO] [stderr] 36 | / impl<F: Clone, const L: usize, const H: usize> Submatrix<[[F; L - 1]; H]> for [[F; L]; H] [INFO] [stderr] 37 | | where [INFO] [stderr] 38 | | Self: Matrix, [INFO] [stderr] 39 | | [[F; L - 1]; H]: Matrix [INFO] [stderr] | |___________________________- first implementation here [INFO] [stderr] ... [INFO] [stderr] 62 | / impl<F: Clone, const L: usize, const H: usize> Submatrix<[[F; L - 1]; H - 1]> for [[F; L]; H] [INFO] [stderr] 63 | | where [INFO] [stderr] 64 | | Self: Matrix, [INFO] [stderr] 65 | | [[F; L - 1]; H - 1]: Matrix [INFO] [stderr] | |_______________________________^ conflicting implementation for `[[_; _]; _]` [INFO] [stderr] [INFO] [stderr] For more information about this error, try `rustc --explain E0119`. [INFO] [stderr] warning: `array-matrix` (lib doc) generated 1 warning [INFO] [stderr] error: could not document `array-matrix` [INFO] running `Command { std: "docker" "inspect" "cc64f254db457c557118cd91f4cae619152afa675c989ae266c20f6bb500ce84", kill_on_drop: false }`