# rustc version rustc 1.93.0-nightly (adaa83897 2025-10-27)
# docs.rs version docsrs 0.6.0 (403e80ef 2025-10-16)
# build log [INFO] running `Command { std: "docker" "create" "-v" "/home/cratesfyi/workspace/builds/jmt-0.12.0/target:/opt/rustwide/target:rw,Z" "-v" "/home/cratesfyi/workspace/builds/jmt-0.12.0/source:/opt/rustwide/workdir:ro,Z" "-v" "/home/cratesfyi/workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/home/cratesfyi/workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "DOCS_RS=1" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "6442450944" "--cpus" "6" "--user" "1001:1001" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+nightly" "rustdoc" "--lib" "-Zrustdoc-map" "--config" "build.rustdocflags=[\"--cfg\", \"docsrs\", \"-Z\", \"unstable-options\", \"--emit=invocation-specific\", \"--resource-suffix\", \"-20251027-1.93.0-nightly-adaa83897\", \"--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: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. [INFO] [stdout] 5948cfa28fbd58da448aa8955a723e9ed06cabc150900302f877525d8cdb0422 [INFO] running `Command { std: "docker" "start" "-a" "5948cfa28fbd58da448aa8955a723e9ed06cabc150900302f877525d8cdb0422", kill_on_drop: false }` [INFO] [stderr] warning: target filter specified, but no targets matched; this is a no-op [INFO] [stderr] Documenting jmt v0.12.0 (/opt/rustwide/workdir) [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/bytes32ext.rs:43:9 [INFO] [stderr] | [INFO] [stderr] 43 | assume!(index < 32 * 2); // assumed precondition [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/bytes32ext.rs:85:9 [INFO] [stderr] | [INFO] [stderr] 85 | assume!(index < self.pos.end); // assumed precondition [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/bytes32ext.rs:86:9 [INFO] [stderr] | [INFO] [stderr] 86 | assume!(self.hash_bytes.len() == 32); // invariant [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/bytes32ext.rs:87:9 [INFO] [stderr] | [INFO] [stderr] 87 | assume!(self.pos.end == self.hash_bytes.len() * 8); // invariant [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:102:9 [INFO] [stderr] | [INFO] [stderr] 102 | checked_precondition!(bytes.len() <= ROOT_NIBBLE_HEIGHT / 2); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `checked_precondition` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `checked_precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `checked_precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:112:9 [INFO] [stderr] | [INFO] [stderr] 112 | checked_precondition!(bytes.len() <= ROOT_NIBBLE_HEIGHT / 2); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `checked_precondition` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `checked_precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `checked_precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:177:9 [INFO] [stderr] | [INFO] [stderr] 177 | assume!(self.num_nibbles <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:186:9 [INFO] [stderr] | [INFO] [stderr] 186 | assume!(self.num_nibbles <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:283:9 [INFO] [stderr] | [INFO] [stderr] 283 | precondition!(start <= end); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:284:9 [INFO] [stderr] | [INFO] [stderr] 284 | precondition!(start <= ROOT_NIBBLE_HEIGHT); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:285:9 [INFO] [stderr] | [INFO] [stderr] 285 | precondition!(end <= ROOT_NIBBLE_HEIGHT); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:295:9 [INFO] [stderr] | [INFO] [stderr] 295 | assume!(self.start <= self.pos.start); // invariant [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:296:9 [INFO] [stderr] | [INFO] [stderr] 296 | assume!(self.pos.start <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:302:9 [INFO] [stderr] | [INFO] [stderr] 302 | assume!(self.pos.start <= self.pos.end); // invariant [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:303:9 [INFO] [stderr] | [INFO] [stderr] 303 | assume!(self.pos.end <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:309:9 [INFO] [stderr] | [INFO] [stderr] 309 | assume!(self.pos.start <= self.pos.end); // invariant [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:310:9 [INFO] [stderr] | [INFO] [stderr] 310 | assume!(self.pos.end <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:327:9 [INFO] [stderr] | [INFO] [stderr] 327 | assume!(self.start <= self.pos.end); // invariant [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/restore.rs:83:9 [INFO] [stderr] | [INFO] [stderr] 83 | precondition!(index < 16); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: public documentation for `Internal` links to private item `InternalNode` [INFO] [stderr] --> src/node_type.rs:882:24 [INFO] [stderr] | [INFO] [stderr] 882 | /// A wrapper of [`InternalNode`]. [INFO] [stderr] | ^^^^^^^^^^^^ this item is private [INFO] [stderr] | [INFO] [stderr] = note: this link will resolve properly if you pass `--document-private-items` [INFO] [stderr] = note: `#[warn(rustdoc::private_intra_doc_links)]` on by default [INFO] [stderr] [INFO] [stderr] warning: unresolved link to `put_value_sets` [INFO] [stderr] --> src/tree.rs:485:19 [INFO] [stderr] | [INFO] [stderr] 485 | /// Same as [`put_value_sets`], this method returns a Merkle proof for every update of the Merkle tree. [INFO] [stderr] | ^^^^^^^^^^^^^^ no item named `put_value_sets` in scope [INFO] [stderr] | [INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]` [INFO] [stderr] = note: `#[warn(rustdoc::broken_intra_doc_links)]` on by default [INFO] [stderr] [INFO] [stderr] warning: unresolved link to `verify_update` [INFO] [stderr] --> src/tree.rs:486:48 [INFO] [stderr] | [INFO] [stderr] 486 | /// The proofs can be verified using the [`verify_update`] method, which requires the old `root_hash`, the `merkle_proof` and the new... [INFO] [stderr] | ^^^^^^^^^^^^^ no item named `verify_update` in scope [INFO] [stderr] | [INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]` [INFO] [stderr] [INFO] [stderr] warning: unresolved link to `JellyfishMerkleTree` [INFO] [stderr] --> src/types/proof/definition.rs:524:37 [INFO] [stderr] | [INFO] [stderr] 524 | /// Verifies an update of the [`JellyfishMerkleTree`], proving the transition from an `old_root_hash` to a `new_root_hash` ([`RootHas... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^ no item named `JellyfishMerkleTree` in scope [INFO] [stderr] | [INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]` [INFO] [stderr] [INFO] [stderr] warning: unresolved link to `JellyfishMerkleTree` [INFO] [stderr] --> src/types/proof/definition.rs:533:48 [INFO] [stderr] | [INFO] [stderr] 533 | /// If these steps are verified then the [`JellyfishMerkleTree`] has been soundly updated [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^ no item named `JellyfishMerkleTree` in scope [INFO] [stderr] | [INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]` [INFO] [stderr] [INFO] [stderr] warning: redundant explicit link target [INFO] [stderr] --> src/lib.rs:108:61 [INFO] [stderr] | [INFO] [stderr] 108 | /// Contains types used to bridge a [`JellyfishMerkleTree`](crate::JellyfishMerkleTree) [INFO] [stderr] | --------------------- ^^^^^^^^^^^^^^^^^^^^^^^^^^ explicit target is redundant [INFO] [stderr] | | [INFO] [stderr] | because label contains path that resolves to same destination [INFO] [stderr] | [INFO] [stderr] = note: when a link's destination is not specified, [INFO] [stderr] the label is used to resolve intra-doc links [INFO] [stderr] = note: `#[warn(rustdoc::redundant_explicit_links)]` on by default [INFO] [stderr] help: remove explicit link target [INFO] [stderr] | [INFO] [stderr] 108 - /// Contains types used to bridge a [`JellyfishMerkleTree`](crate::JellyfishMerkleTree) [INFO] [stderr] 108 + /// Contains types used to bridge a [`JellyfishMerkleTree`] [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: `jmt` (lib doc) generated 25 warnings [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.88s [INFO] [stderr] Generated /opt/rustwide/target/x86_64-unknown-linux-gnu/doc/jmt/index.html [INFO] running `Command { std: "docker" "inspect" "5948cfa28fbd58da448aa8955a723e9ed06cabc150900302f877525d8cdb0422", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "5948cfa28fbd58da448aa8955a723e9ed06cabc150900302f877525d8cdb0422", kill_on_drop: false }` [INFO] [stdout] 5948cfa28fbd58da448aa8955a723e9ed06cabc150900302f877525d8cdb0422