# rustc version rustc 1.98.0-nightly (cb46fbb8c 2026-06-08)
# docs.rs version docsrs 0.0.0 (39849b9c22c419f6b690c8d2213455bc7426a6b8 2026-06-03 )
# 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" "fce02a729994e18804a3023badf2d742af96148bd5abf2275a40224190f4cf34" "/opt/rustwide/cargo-home/bin/cargo" "+nightly" "rustdoc" "--lib" "-Zrustdoc-map" "--features" "full" "--config" "build.rustdocflags=[\"--cfg\", \"docsrs\", \"-Z\", \"unstable-options\", \"--emit=invocation-specific\", \"--resource-suffix\", \"-20260608-1.98.0-nightly-cb46fbb8c\", \"--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: Rustdoc did not scrape the following examples because they require dev-dependencies: asbytes_as_bytes_trivial, asbytes_into_bytes_trivial [INFO] [stderr] If you want Rustdoc to scrape these examples, then add `doc-scrape-examples = true` [INFO] [stderr] to the [[example]] target configuration of at least one example. [INFO] [stderr] warning: target filter specified, but no targets matched; this is a no-op [INFO] [stderr] Documenting asbytes v0.3.0 (/opt/rustwide/workdir) [INFO] [stderr] warning: unresolved link to `T` [INFO] [stderr] --> src/as_bytes.rs:87:27 [INFO] [stderr] | [INFO] [stderr] 87 | /// Implementation for [T] where T is POD. [INFO] [stderr] | ^ no item named `T` 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 `T` [INFO] [stderr] --> src/into_bytes.rs:99:29 [INFO] [stderr] | [INFO] [stderr] 99 | /// Implementation for &[ T] where T is Pod. [INFO] [stderr] | ^ no item named `T` in scope [INFO] [stderr] | [INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]` [INFO] [stderr] [INFO] [stderr] warning: unresolved link to `T` [INFO] [stderr] --> src/into_bytes.rs:111:32 [INFO] [stderr] | [INFO] [stderr] 111 | /// Implementation for Box< [T] > where T is POD. [INFO] [stderr] | ^ no item named `T` in scope [INFO] [stderr] | [INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]` [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `u8` [INFO] [stderr] --> /opt/rustwide/workdir/readme.md:86:148 [INFO] [stderr] | [INFO] [stderr] 86 | ...different data types to an I/O stream (simulated here by a Vec<u8>). The generic send_data function accepts any type T that imple... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(rustdoc::invalid_html_tags)]` on by default [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 86 | This example showcases the IntoBytes trait, demonstrating how it facilitates writing different data types to an I/O stream (simulated here by a `Vec<u8>`). The generic send_data function accepts any type T that implements IntoBytes. Inside the function, data.into_bytes() consumes the input data and returns an owned Vec<u8>. This owned vector is necessary when the receiving function or operation (like writer.write_all) requires ownership or when the data needs to live beyond the current scope (e.g., in asynchronous operations). The example sends a POD struct (with explicit padding for Pod safety), a String, a Vec<f32>, and an array, showing how IntoBytes provides a uniform way to prepare diverse data for serialization or transmission. Note that types like String and Vec are moved and consumed, while Copy types are technically moved but the original variable remains usable due to the copy. [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `u8` [INFO] [stderr] --> /opt/rustwide/workdir/readme.md:86:319 [INFO] [stderr] | [INFO] [stderr] 86 | ....into_bytes() consumes the input data and returns an owned Vec<u8>. This owned vector is necessary when the receiving function or... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 86 | This example showcases the IntoBytes trait, demonstrating how it facilitates writing different data types to an I/O stream (simulated here by a Vec<u8>). The generic send_data function accepts any type T that implements IntoBytes. Inside the function, data.into_bytes() consumes the input data and returns an owned `Vec<u8>`. This owned vector is necessary when the receiving function or operation (like writer.write_all) requires ownership or when the data needs to live beyond the current scope (e.g., in asynchronous operations). The example sends a POD struct (with explicit padding for Pod safety), a String, a Vec<f32>, and an array, showing how IntoBytes provides a uniform way to prepare diverse data for serialization or transmission. Note that types like String and Vec are moved and consumed, while Copy types are technically moved but the original variable remains usable due to the copy. [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `f32` [INFO] [stderr] --> /opt/rustwide/workdir/readme.md:86:618 [INFO] [stderr] | [INFO] [stderr] 86 | ...struct (with explicit padding for Pod safety), a String, a Vec<f32>, and an array, showing how IntoBytes provides a uniform way t... [INFO] [stderr] | ^^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 86 | This example showcases the IntoBytes trait, demonstrating how it facilitates writing different data types to an I/O stream (simulated here by a Vec<u8>). The generic send_data function accepts any type T that implements IntoBytes. Inside the function, data.into_bytes() consumes the input data and returns an owned Vec<u8>. This owned vector is necessary when the receiving function or operation (like writer.write_all) requires ownership or when the data needs to live beyond the current scope (e.g., in asynchronous operations). The example sends a POD struct (with explicit padding for Pod safety), a String, a `Vec<f32>`, and an array, showing how IntoBytes provides a uniform way to prepare diverse data for serialization or transmission. Note that types like String and Vec are moved and consumed, while Copy types are technically moved but the original variable remains usable due to the copy. [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: `asbytes` (lib doc) generated 6 warnings [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.37s [INFO] [stderr] Generated /opt/rustwide/target/x86_64-unknown-linux-gnu/doc/asbytes/index.html [INFO] running `Command { std: "docker" "inspect" "fce02a729994e18804a3023badf2d742af96148bd5abf2275a40224190f4cf34", kill_on_drop: false }`