# rustc version rustc 1.96.0-nightly (fb27476aa 2026-03-28)
# docs.rs version docsrs 0.0.0 (da7690ee 2026-03-15 )
# build log [INFO] running `Command { std: "docker" "create" "-v" "/home/cratesfyi/workspace-builder3/builds/iri-string-0.7.12/target:/opt/rustwide/target:rw,Z" "-v" "/home/cratesfyi/workspace-builder3/builds/iri-string-0.7.12/source:/opt/rustwide/workdir:ro,Z" "-v" "/home/cratesfyi/workspace-builder3/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/home/cratesfyi/workspace-builder3/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:d429b63d4308055ea97f60fb1d3dfca48854a00942f1bd2ad806beaf015945ec" "/opt/rustwide/cargo-home/bin/cargo" "+nightly" "rustdoc" "--lib" "-Zrustdoc-map" "--all-features" "--config" "build.rustdocflags=[\"--cfg\", \"docsrs\", \"--cfg\", \"docsrs\", \"-Z\", \"unstable-options\", \"--emit=invocation-specific\", \"--resource-suffix\", \"-20260328-1.96.0-nightly-fb27476aa\", \"--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] 02325ec4e63faf362edbef0f5a7c119680c035e0ed68bfa57ed37544767cc40f [INFO] running `Command { std: "docker" "start" "-a" "02325ec4e63faf362edbef0f5a7c119680c035e0ed68bfa57ed37544767cc40f", kill_on_drop: false }` [INFO] [stderr] warning: Rustdoc did not scrape the following examples because they require dev-dependencies: flamegraph-parse, flamegraph-resolve, normalize, parse, resolve [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 iri-string v0.7.12 (/opt/rustwide/workdir) [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/template/string/owned.rs:33:38 [INFO] [stderr] | [INFO] [stderr] 33 | #[cfg_attr(feature = "serde", derive(serde::Serialize))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `alloc`, `default`, `memchr`, `serde`, and `std` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive` [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 derive macro `serde::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/template/string.rs:83:38 [INFO] [stderr] | [INFO] [stderr] 83 | #[cfg_attr(feature = "serde", derive(serde::Serialize))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `alloc`, `default`, `memchr`, `serde`, and `std` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive` [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 derive macro `serde::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/types/generic/macros.rs:179:46 [INFO] [stderr] | [INFO] [stderr] 179 | #[cfg_attr(feature = "serde", derive(serde::Serialize))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/types/generic/absolute.rs:18:1 [INFO] [stderr] | [INFO] [stderr] 18 | / define_custom_string_slice! { [INFO] [stderr] 19 | | /// A borrowed slice of an absolute IRI without fragment part. [INFO] [stderr] 20 | | /// [INFO] [stderr] 21 | | /// This corresponds to [`absolute-IRI` rule] in [RFC 3987] [INFO] [stderr] ... | [INFO] [stderr] 89 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `alloc`, `default`, `memchr`, `serde`, and `std` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive` [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 derive macro `serde::Serialize` which comes from the expansion of the macro `define_custom_string_slice` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/types/generic/macros.rs:545:70 [INFO] [stderr] | [INFO] [stderr] 545 | #[cfg_attr(all(feature = "serde", feature = "alloc"), derive(serde::Serialize))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/types/generic/absolute.rs:92:1 [INFO] [stderr] | [INFO] [stderr] 92 | / define_custom_string_owned! { [INFO] [stderr] 93 | | /// An owned string of an absolute IRI without fragment part. [INFO] [stderr] 94 | | /// [INFO] [stderr] 95 | | /// This corresponds to [`absolute-IRI` rule] in [RFC 3987] [INFO] [stderr] ... | [INFO] [stderr] 117 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `alloc`, `default`, `memchr`, `serde`, and `std` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive` [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 derive macro `serde::Serialize` which comes from the expansion of the macro `define_custom_string_owned` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/types/generic/macros.rs:179:46 [INFO] [stderr] | [INFO] [stderr] 179 | #[cfg_attr(feature = "serde", derive(serde::Serialize))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/types/generic/fragment.rs:6:1 [INFO] [stderr] | [INFO] [stderr] 6 | / define_custom_string_slice! { [INFO] [stderr] 7 | | /// A borrowed slice of an IRI fragment (i.e. after the first `#` character). [INFO] [stderr] 8 | | /// [INFO] [stderr] 9 | | /// This corresponds to [`ifragment` rule] in [RFC 3987] (and [`fragment` rule] in [RFC 3986]). [INFO] [stderr] ... | [INFO] [stderr] 49 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `alloc`, `default`, `memchr`, `serde`, and `std` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive` [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 derive macro `serde::Serialize` which comes from the expansion of the macro `define_custom_string_slice` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/types/generic/macros.rs:545:70 [INFO] [stderr] | [INFO] [stderr] 545 | #[cfg_attr(all(feature = "serde", feature = "alloc"), derive(serde::Serialize))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/types/generic/fragment.rs:52:1 [INFO] [stderr] | [INFO] [stderr] 52 | / define_custom_string_owned! { [INFO] [stderr] 53 | | /// An owned string of an IRI fragment (i.e. after the first `#` character). [INFO] [stderr] 54 | | /// [INFO] [stderr] 55 | | /// This corresponds to [`ifragment` rule] in [RFC 3987] (and [`fragment` rule] in [RFC 3986]). [INFO] [stderr] ... | [INFO] [stderr] 72 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `alloc`, `default`, `memchr`, `serde`, and `std` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive` [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 derive macro `serde::Serialize` which comes from the expansion of the macro `define_custom_string_owned` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/types/generic/macros.rs:179:46 [INFO] [stderr] | [INFO] [stderr] 179 | #[cfg_attr(feature = "serde", derive(serde::Serialize))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/types/generic/normal.rs:22:1 [INFO] [stderr] | [INFO] [stderr] 22 | / define_custom_string_slice! { [INFO] [stderr] 23 | | /// A borrowed string of an absolute IRI possibly with fragment part. [INFO] [stderr] 24 | | /// [INFO] [stderr] 25 | | /// This corresponds to [`IRI` rule] in [RFC 3987] (and [`URI` rule] in [RFC 3986]). [INFO] [stderr] ... | [INFO] [stderr] 86 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `alloc`, `default`, `memchr`, `serde`, and `std` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive` [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 derive macro `serde::Serialize` which comes from the expansion of the macro `define_custom_string_slice` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/types/generic/macros.rs:545:70 [INFO] [stderr] | [INFO] [stderr] 545 | #[cfg_attr(all(feature = "serde", feature = "alloc"), derive(serde::Serialize))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/types/generic/normal.rs:89:1 [INFO] [stderr] | [INFO] [stderr] 89 | / define_custom_string_owned! { [INFO] [stderr] 90 | | /// An owned string of an absolute IRI possibly with fragment part. [INFO] [stderr] 91 | | /// [INFO] [stderr] 92 | | /// This corresponds to [`IRI` rule] in [RFC 3987] (and [`URI` rule] in [RFC 3986]). [INFO] [stderr] ... | [INFO] [stderr] 110 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `alloc`, `default`, `memchr`, `serde`, and `std` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive` [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 derive macro `serde::Serialize` which comes from the expansion of the macro `define_custom_string_owned` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/types/generic/macros.rs:179:46 [INFO] [stderr] | [INFO] [stderr] 179 | #[cfg_attr(feature = "serde", derive(serde::Serialize))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/types/generic/query.rs:6:1 [INFO] [stderr] | [INFO] [stderr] 6 | / define_custom_string_slice! { [INFO] [stderr] 7 | | /// A borrowed slice of an IRI query (i.e. after the first `?` and before the first `#`). [INFO] [stderr] 8 | | /// [INFO] [stderr] 9 | | /// This corresponds to [`iquery` rule] in [RFC 3987] (and [`query` rule] in [RFC 3986]). [INFO] [stderr] ... | [INFO] [stderr] 74 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `alloc`, `default`, `memchr`, `serde`, and `std` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive` [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 derive macro `serde::Serialize` which comes from the expansion of the macro `define_custom_string_slice` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/types/generic/macros.rs:545:70 [INFO] [stderr] | [INFO] [stderr] 545 | #[cfg_attr(all(feature = "serde", feature = "alloc"), derive(serde::Serialize))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/types/generic/query.rs:77:1 [INFO] [stderr] | [INFO] [stderr] 77 | / define_custom_string_owned! { [INFO] [stderr] 78 | | /// An owned string of an IRI fragment (i.e. after the first `#` character). [INFO] [stderr] 79 | | /// [INFO] [stderr] 80 | | /// This corresponds to [`iquery` rule] in [RFC 3987] (and [`query` rule] in [RFC 3986]). [INFO] [stderr] ... | [INFO] [stderr] 97 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `alloc`, `default`, `memchr`, `serde`, and `std` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive` [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 derive macro `serde::Serialize` which comes from the expansion of the macro `define_custom_string_owned` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/types/generic/macros.rs:179:46 [INFO] [stderr] | [INFO] [stderr] 179 | #[cfg_attr(feature = "serde", derive(serde::Serialize))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/types/generic/reference.rs:23:1 [INFO] [stderr] | [INFO] [stderr] 23 | / define_custom_string_slice! { [INFO] [stderr] 24 | | /// A borrowed string of an absolute IRI possibly with fragment part. [INFO] [stderr] 25 | | /// [INFO] [stderr] 26 | | /// This corresponds to [`IRI-reference` rule] in [RFC 3987] [INFO] [stderr] ... | [INFO] [stderr] 76 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `alloc`, `default`, `memchr`, `serde`, and `std` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive` [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 derive macro `serde::Serialize` which comes from the expansion of the macro `define_custom_string_slice` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/types/generic/macros.rs:545:70 [INFO] [stderr] | [INFO] [stderr] 545 | #[cfg_attr(all(feature = "serde", feature = "alloc"), derive(serde::Serialize))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/types/generic/reference.rs:79:1 [INFO] [stderr] | [INFO] [stderr] 79 | / define_custom_string_owned! { [INFO] [stderr] 80 | | /// An owned string of an absolute IRI possibly with fragment part. [INFO] [stderr] 81 | | /// [INFO] [stderr] 82 | | /// This corresponds to [`IRI-reference` rule] in [RFC 3987] [INFO] [stderr] ... | [INFO] [stderr] 103 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `alloc`, `default`, `memchr`, `serde`, and `std` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive` [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 derive macro `serde::Serialize` which comes from the expansion of the macro `define_custom_string_owned` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/types/generic/macros.rs:179:46 [INFO] [stderr] | [INFO] [stderr] 179 | #[cfg_attr(feature = "serde", derive(serde::Serialize))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/types/generic/relative.rs:21:1 [INFO] [stderr] | [INFO] [stderr] 21 | / define_custom_string_slice! { [INFO] [stderr] 22 | | /// A borrowed slice of a relative IRI reference. [INFO] [stderr] 23 | | /// [INFO] [stderr] 24 | | /// This corresponds to [`irelative-ref` rule] in [RFC 3987] [INFO] [stderr] ... | [INFO] [stderr] 82 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `alloc`, `default`, `memchr`, `serde`, and `std` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive` [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 derive macro `serde::Serialize` which comes from the expansion of the macro `define_custom_string_slice` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/types/generic/macros.rs:545:70 [INFO] [stderr] | [INFO] [stderr] 545 | #[cfg_attr(all(feature = "serde", feature = "alloc"), derive(serde::Serialize))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/types/generic/relative.rs:85:1 [INFO] [stderr] | [INFO] [stderr] 85 | / define_custom_string_owned! { [INFO] [stderr] 86 | | /// An owned string of a relative IRI reference. [INFO] [stderr] 87 | | /// [INFO] [stderr] 88 | | /// This corresponds to [`irelative-ref` rule] in [RFC 3987] [INFO] [stderr] ... | [INFO] [stderr] 106 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `alloc`, `default`, `memchr`, `serde`, and `std` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive` [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 derive macro `serde::Serialize` which comes from the expansion of the macro `define_custom_string_owned` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: `iri-string` (lib doc) generated 14 warnings [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 1.31s [INFO] [stderr] Generated /opt/rustwide/target/x86_64-unknown-linux-gnu/doc/iri_string/index.html [INFO] running `Command { std: "docker" "inspect" "02325ec4e63faf362edbef0f5a7c119680c035e0ed68bfa57ed37544767cc40f", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "02325ec4e63faf362edbef0f5a7c119680c035e0ed68bfa57ed37544767cc40f", kill_on_drop: false }` [INFO] [stdout] 02325ec4e63faf362edbef0f5a7c119680c035e0ed68bfa57ed37544767cc40f