[INFO] fetching crate rxml_validation 0.11.0... [INFO] checking rxml_validation-0.11.0 against try#4d98531622e1718ae0bc3c7a1ab9cd8938428452+rustflags=-Dtail_expr_drop_order for pr-129604 [INFO] extracting crate rxml_validation 0.11.0 into /workspace/builds/worker-3-tc2/source [INFO] validating manifest of crates.io crate rxml_validation 0.11.0 on toolchain 4d98531622e1718ae0bc3c7a1ab9cd8938428452 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+4d98531622e1718ae0bc3c7a1ab9cd8938428452" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] started tweaking crates.io crate rxml_validation 0.11.0 [INFO] finished tweaking crates.io crate rxml_validation 0.11.0 [INFO] tweaked toml for crates.io crate rxml_validation 0.11.0 written to /workspace/builds/worker-3-tc2/source/Cargo.toml [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+4d98531622e1718ae0bc3c7a1ab9cd8938428452" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Updating crates.io index [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Locking 8 packages to latest compatible versions [INFO] [stderr] Adding compact_str v0.7.1 (latest: v0.8.0) [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+4d98531622e1718ae0bc3c7a1ab9cd8938428452" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:923055f121b5182466d55868a8b05e67af8ba4a3a3f6bad814e953ca3cd3ac2a" "/opt/rustwide/cargo-home/bin/cargo" "+4d98531622e1718ae0bc3c7a1ab9cd8938428452" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] ba3763c2c3bbafeab2a2b6ac7affa163f7c9fdb6083dac06c4affd76349ca44d [INFO] running `Command { std: "docker" "start" "-a" "ba3763c2c3bbafeab2a2b6ac7affa163f7c9fdb6083dac06c4affd76349ca44d", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "ba3763c2c3bbafeab2a2b6ac7affa163f7c9fdb6083dac06c4affd76349ca44d", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "ba3763c2c3bbafeab2a2b6ac7affa163f7c9fdb6083dac06c4affd76349ca44d", kill_on_drop: false }` [INFO] [stdout] ba3763c2c3bbafeab2a2b6ac7affa163f7c9fdb6083dac06c4affd76349ca44d [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid -Dtail_expr_drop_order" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:923055f121b5182466d55868a8b05e67af8ba4a3a3f6bad814e953ca3cd3ac2a" "/opt/rustwide/cargo-home/bin/cargo" "+4d98531622e1718ae0bc3c7a1ab9cd8938428452" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] d20283282f9fb6fa327931bc627a9b073b3f28a22cc47d8ce6fa976da941e7cd [INFO] running `Command { std: "docker" "start" "-a" "d20283282f9fb6fa327931bc627a9b073b3f28a22cc47d8ce6fa976da941e7cd", kill_on_drop: false }` [INFO] [stderr] Checking castaway v0.2.3 [INFO] [stderr] Checking compact_str v0.7.1 [INFO] [stderr] Checking rxml_validation v0.11.0 (/opt/rustwide/workdir) [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:342:10 [INFO] [stdout] | [INFO] [stdout] 341 | pub unsafe fn from_str_unchecked>(s: T) -> Self { [INFO] [stdout] | ---- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 342 | Self(s.as_ref().into()) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 937 | / rxml_custom_string_type_pair! { [INFO] [stdout] 938 | | /// String which conforms to the Name production of XML 1.0. [INFO] [stdout] 939 | | /// [INFO] [stdout] 940 | | /// [`Name`] corresponds to a (restricted) [`String`]. For a [`str`]-like type [INFO] [stdout] ... | [INFO] [stdout] 981 | | pub struct NameStr(str); [INFO] [stdout] 982 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: requested on the command line with `-D tail-expr-drop-order` [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:347:10 [INFO] [stdout] | [INFO] [stdout] 346 | pub unsafe fn from_string_unchecked>(s: T) -> Self { [INFO] [stdout] | ---- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 347 | Self(s.into().into()) [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 937 | / rxml_custom_string_type_pair! { [INFO] [stdout] 938 | | /// String which conforms to the Name production of XML 1.0. [INFO] [stdout] 939 | | /// [INFO] [stdout] 940 | | /// [`Name`] corresponds to a (restricted) [`String`]. For a [`str`]-like type [INFO] [stdout] ... | [INFO] [stdout] 981 | | pub struct NameStr(str); [INFO] [stdout] 982 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:353:10 [INFO] [stdout] | [INFO] [stdout] 352 | unsafe fn from_auto_unchecked(s: CompactString) -> Self { [INFO] [stdout] | ---------------- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 353 | Self(s.into()) [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 937 | / rxml_custom_string_type_pair! { [INFO] [stdout] 938 | | /// String which conforms to the Name production of XML 1.0. [INFO] [stdout] 939 | | /// [INFO] [stdout] 940 | | /// [`Name`] corresponds to a (restricted) [`String`]. For a [`str`]-like type [INFO] [stdout] ... | [INFO] [stdout] 981 | | pub struct NameStr(str); [INFO] [stdout] 982 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:366:10 [INFO] [stdout] | [INFO] [stdout] 365 | pub unsafe fn from_compact_str_unchecked>(s: T) -> Self { [INFO] [stdout] | ---- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 366 | Self(s.into().into()) [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 937 | / rxml_custom_string_type_pair! { [INFO] [stdout] 938 | | /// String which conforms to the Name production of XML 1.0. [INFO] [stdout] 939 | | /// [INFO] [stdout] 940 | | /// [`Name`] corresponds to a (restricted) [`String`]. For a [`str`]-like type [INFO] [stdout] ... | [INFO] [stdout] 981 | | pub struct NameStr(str); [INFO] [stdout] 982 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:537:8 [INFO] [stdout] | [INFO] [stdout] 535 | fn try_from(other: CompactString) -> Result { [INFO] [stdout] | -------------------- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 536 | $check(&other)?; [INFO] [stdout] 537 | Ok($name(other.into())) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 937 | / rxml_custom_string_type_pair! { [INFO] [stdout] 938 | | /// String which conforms to the Name production of XML 1.0. [INFO] [stdout] 939 | | /// [INFO] [stdout] 940 | | /// [`Name`] corresponds to a (restricted) [`String`]. For a [`str`]-like type [INFO] [stdout] ... | [INFO] [stdout] 981 | | pub struct NameStr(str); [INFO] [stdout] 982 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:595:19 [INFO] [stdout] | [INFO] [stdout] 594 | fn extend>(&mut self, iter: I) { [INFO] [stdout] | ------- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 595 | self.0.extend(iter.into_iter().map(|x| &x.0)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 937 | / rxml_custom_string_type_pair! { [INFO] [stdout] 938 | | /// String which conforms to the Name production of XML 1.0. [INFO] [stdout] 939 | | /// [INFO] [stdout] 940 | | /// [`Name`] corresponds to a (restricted) [`String`]. For a [`str`]-like type [INFO] [stdout] ... | [INFO] [stdout] 981 | | pub struct NameStr(str); [INFO] [stdout] 982 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:617:19 [INFO] [stdout] | [INFO] [stdout] 616 | fn extend>(&mut self, iter: I) { [INFO] [stdout] | ------- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 617 | self.0.extend(iter.into_iter().map(|x| x.0)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 937 | / rxml_custom_string_type_pair! { [INFO] [stdout] 938 | | /// String which conforms to the Name production of XML 1.0. [INFO] [stdout] 939 | | /// [INFO] [stdout] 940 | | /// [`Name`] corresponds to a (restricted) [`String`]. For a [`str`]-like type [INFO] [stdout] ... | [INFO] [stdout] 981 | | pub struct NameStr(str); [INFO] [stdout] 982 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:1051:6 [INFO] [stdout] | [INFO] [stdout] 1022 | pub fn split_name(self) -> Result<(Option, NcName), Error> { [INFO] [stdout] | ---- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 1023 | let mut name = self.0; [INFO] [stdout] | ---- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] ... [INFO] [stdout] 1032 | let localname = name.split_off(colon_pos + 1); [INFO] [stdout] | --------- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 1033 | let mut prefix = name; [INFO] [stdout] | ------ these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] ... [INFO] [stdout] 1051 | Ok(( [INFO] [stdout] | ____________^ [INFO] [stdout] 1052 | | Some(unsafe { NcName::from_auto_unchecked(prefix) }), [INFO] [stdout] 1053 | | unsafe { NcName::from_auto_unchecked(localname) }, [INFO] [stdout] 1054 | | )) [INFO] [stdout] | |_________^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:342:10 [INFO] [stdout] | [INFO] [stdout] 341 | pub unsafe fn from_str_unchecked>(s: T) -> Self { [INFO] [stdout] | ---- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 342 | Self(s.as_ref().into()) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 1141 | / rxml_custom_string_type_pair! { [INFO] [stdout] 1142 | | /// String which conforms to the NcName production of Namespaces in XML 1.0. [INFO] [stdout] 1143 | | /// [INFO] [stdout] 1144 | | /// [`NcName`] corresponds to a (restricted) [`String`]. For a [`str`]-like [INFO] [stdout] ... | [INFO] [stdout] 1177 | | pub struct NcNameStr(str); [INFO] [stdout] 1178 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:347:10 [INFO] [stdout] | [INFO] [stdout] 346 | pub unsafe fn from_string_unchecked>(s: T) -> Self { [INFO] [stdout] | ---- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 347 | Self(s.into().into()) [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 1141 | / rxml_custom_string_type_pair! { [INFO] [stdout] 1142 | | /// String which conforms to the NcName production of Namespaces in XML 1.0. [INFO] [stdout] 1143 | | /// [INFO] [stdout] 1144 | | /// [`NcName`] corresponds to a (restricted) [`String`]. For a [`str`]-like [INFO] [stdout] ... | [INFO] [stdout] 1177 | | pub struct NcNameStr(str); [INFO] [stdout] 1178 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:353:10 [INFO] [stdout] | [INFO] [stdout] 352 | unsafe fn from_auto_unchecked(s: CompactString) -> Self { [INFO] [stdout] | ---------------- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 353 | Self(s.into()) [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 1141 | / rxml_custom_string_type_pair! { [INFO] [stdout] 1142 | | /// String which conforms to the NcName production of Namespaces in XML 1.0. [INFO] [stdout] 1143 | | /// [INFO] [stdout] 1144 | | /// [`NcName`] corresponds to a (restricted) [`String`]. For a [`str`]-like [INFO] [stdout] ... | [INFO] [stdout] 1177 | | pub struct NcNameStr(str); [INFO] [stdout] 1178 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:366:10 [INFO] [stdout] | [INFO] [stdout] 365 | pub unsafe fn from_compact_str_unchecked>(s: T) -> Self { [INFO] [stdout] | ---- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 366 | Self(s.into().into()) [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 1141 | / rxml_custom_string_type_pair! { [INFO] [stdout] 1142 | | /// String which conforms to the NcName production of Namespaces in XML 1.0. [INFO] [stdout] 1143 | | /// [INFO] [stdout] 1144 | | /// [`NcName`] corresponds to a (restricted) [`String`]. For a [`str`]-like [INFO] [stdout] ... | [INFO] [stdout] 1177 | | pub struct NcNameStr(str); [INFO] [stdout] 1178 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:537:8 [INFO] [stdout] | [INFO] [stdout] 535 | fn try_from(other: CompactString) -> Result { [INFO] [stdout] | -------------------- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 536 | $check(&other)?; [INFO] [stdout] 537 | Ok($name(other.into())) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 1141 | / rxml_custom_string_type_pair! { [INFO] [stdout] 1142 | | /// String which conforms to the NcName production of Namespaces in XML 1.0. [INFO] [stdout] 1143 | | /// [INFO] [stdout] 1144 | | /// [`NcName`] corresponds to a (restricted) [`String`]. For a [`str`]-like [INFO] [stdout] ... | [INFO] [stdout] 1177 | | pub struct NcNameStr(str); [INFO] [stdout] 1178 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:595:19 [INFO] [stdout] | [INFO] [stdout] 594 | fn extend>(&mut self, iter: I) { [INFO] [stdout] | ------- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 595 | self.0.extend(iter.into_iter().map(|x| &x.0)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 1141 | / rxml_custom_string_type_pair! { [INFO] [stdout] 1142 | | /// String which conforms to the NcName production of Namespaces in XML 1.0. [INFO] [stdout] 1143 | | /// [INFO] [stdout] 1144 | | /// [`NcName`] corresponds to a (restricted) [`String`]. For a [`str`]-like [INFO] [stdout] ... | [INFO] [stdout] 1177 | | pub struct NcNameStr(str); [INFO] [stdout] 1178 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:617:19 [INFO] [stdout] | [INFO] [stdout] 616 | fn extend>(&mut self, iter: I) { [INFO] [stdout] | ------- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 617 | self.0.extend(iter.into_iter().map(|x| x.0)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 1141 | / rxml_custom_string_type_pair! { [INFO] [stdout] 1142 | | /// String which conforms to the NcName production of Namespaces in XML 1.0. [INFO] [stdout] 1143 | | /// [INFO] [stdout] 1144 | | /// [`NcName`] corresponds to a (restricted) [`String`]. For a [`str`]-like [INFO] [stdout] ... | [INFO] [stdout] 1177 | | pub struct NcNameStr(str); [INFO] [stdout] 1178 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: aborting due to 15 previous errors [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:342:10 [INFO] [stdout] | [INFO] [stdout] 341 | pub unsafe fn from_str_unchecked>(s: T) -> Self { [INFO] [stdout] | ---- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 342 | Self(s.as_ref().into()) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 937 | / rxml_custom_string_type_pair! { [INFO] [stdout] 938 | | /// String which conforms to the Name production of XML 1.0. [INFO] [stdout] 939 | | /// [INFO] [stdout] 940 | | /// [`Name`] corresponds to a (restricted) [`String`]. For a [`str`]-like type [INFO] [stdout] ... | [INFO] [stdout] 981 | | pub struct NameStr(str); [INFO] [stdout] 982 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: requested on the command line with `-D tail-expr-drop-order` [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:347:10 [INFO] [stdout] | [INFO] [stdout] 346 | pub unsafe fn from_string_unchecked>(s: T) -> Self { [INFO] [stdout] | ---- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 347 | Self(s.into().into()) [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 937 | / rxml_custom_string_type_pair! { [INFO] [stdout] 938 | | /// String which conforms to the Name production of XML 1.0. [INFO] [stdout] 939 | | /// [INFO] [stdout] 940 | | /// [`Name`] corresponds to a (restricted) [`String`]. For a [`str`]-like type [INFO] [stdout] ... | [INFO] [stdout] 981 | | pub struct NameStr(str); [INFO] [stdout] 982 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:353:10 [INFO] [stdout] | [INFO] [stdout] 352 | unsafe fn from_auto_unchecked(s: CompactString) -> Self { [INFO] [stdout] | ---------------- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 353 | Self(s.into()) [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 937 | / rxml_custom_string_type_pair! { [INFO] [stdout] 938 | | /// String which conforms to the Name production of XML 1.0. [INFO] [stdout] 939 | | /// [INFO] [stdout] 940 | | /// [`Name`] corresponds to a (restricted) [`String`]. For a [`str`]-like type [INFO] [stdout] ... | [INFO] [stdout] 981 | | pub struct NameStr(str); [INFO] [stdout] 982 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:366:10 [INFO] [stdout] | [INFO] [stdout] 365 | pub unsafe fn from_compact_str_unchecked>(s: T) -> Self { [INFO] [stdout] | ---- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 366 | Self(s.into().into()) [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 937 | / rxml_custom_string_type_pair! { [INFO] [stdout] 938 | | /// String which conforms to the Name production of XML 1.0. [INFO] [stdout] 939 | | /// [INFO] [stdout] 940 | | /// [`Name`] corresponds to a (restricted) [`String`]. For a [`str`]-like type [INFO] [stdout] ... | [INFO] [stdout] 981 | | pub struct NameStr(str); [INFO] [stdout] 982 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `rxml_validation` (lib) due to 16 previous errors [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:537:8 [INFO] [stdout] | [INFO] [stdout] 535 | fn try_from(other: CompactString) -> Result { [INFO] [stdout] | -------------------- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 536 | $check(&other)?; [INFO] [stdout] 537 | Ok($name(other.into())) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 937 | / rxml_custom_string_type_pair! { [INFO] [stdout] 938 | | /// String which conforms to the Name production of XML 1.0. [INFO] [stdout] 939 | | /// [INFO] [stdout] 940 | | /// [`Name`] corresponds to a (restricted) [`String`]. For a [`str`]-like type [INFO] [stdout] ... | [INFO] [stdout] 981 | | pub struct NameStr(str); [INFO] [stdout] 982 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:595:19 [INFO] [stdout] | [INFO] [stdout] 594 | fn extend>(&mut self, iter: I) { [INFO] [stdout] | ------- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 595 | self.0.extend(iter.into_iter().map(|x| &x.0)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 937 | / rxml_custom_string_type_pair! { [INFO] [stdout] 938 | | /// String which conforms to the Name production of XML 1.0. [INFO] [stdout] 939 | | /// [INFO] [stdout] 940 | | /// [`Name`] corresponds to a (restricted) [`String`]. For a [`str`]-like type [INFO] [stdout] ... | [INFO] [stdout] 981 | | pub struct NameStr(str); [INFO] [stdout] 982 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:617:19 [INFO] [stdout] | [INFO] [stdout] 616 | fn extend>(&mut self, iter: I) { [INFO] [stdout] | ------- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 617 | self.0.extend(iter.into_iter().map(|x| x.0)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 937 | / rxml_custom_string_type_pair! { [INFO] [stdout] 938 | | /// String which conforms to the Name production of XML 1.0. [INFO] [stdout] 939 | | /// [INFO] [stdout] 940 | | /// [`Name`] corresponds to a (restricted) [`String`]. For a [`str`]-like type [INFO] [stdout] ... | [INFO] [stdout] 981 | | pub struct NameStr(str); [INFO] [stdout] 982 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:1051:6 [INFO] [stdout] | [INFO] [stdout] 1022 | pub fn split_name(self) -> Result<(Option, NcName), Error> { [INFO] [stdout] | ---- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 1023 | let mut name = self.0; [INFO] [stdout] | ---- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] ... [INFO] [stdout] 1032 | let localname = name.split_off(colon_pos + 1); [INFO] [stdout] | --------- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 1033 | let mut prefix = name; [INFO] [stdout] | ------ these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] ... [INFO] [stdout] 1051 | Ok(( [INFO] [stdout] | ____________^ [INFO] [stdout] 1052 | | Some(unsafe { NcName::from_auto_unchecked(prefix) }), [INFO] [stdout] 1053 | | unsafe { NcName::from_auto_unchecked(localname) }, [INFO] [stdout] 1054 | | )) [INFO] [stdout] | |_________^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:342:10 [INFO] [stdout] | [INFO] [stdout] 341 | pub unsafe fn from_str_unchecked>(s: T) -> Self { [INFO] [stdout] | ---- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 342 | Self(s.as_ref().into()) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 1141 | / rxml_custom_string_type_pair! { [INFO] [stdout] 1142 | | /// String which conforms to the NcName production of Namespaces in XML 1.0. [INFO] [stdout] 1143 | | /// [INFO] [stdout] 1144 | | /// [`NcName`] corresponds to a (restricted) [`String`]. For a [`str`]-like [INFO] [stdout] ... | [INFO] [stdout] 1177 | | pub struct NcNameStr(str); [INFO] [stdout] 1178 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:347:10 [INFO] [stdout] | [INFO] [stdout] 346 | pub unsafe fn from_string_unchecked>(s: T) -> Self { [INFO] [stdout] | ---- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 347 | Self(s.into().into()) [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 1141 | / rxml_custom_string_type_pair! { [INFO] [stdout] 1142 | | /// String which conforms to the NcName production of Namespaces in XML 1.0. [INFO] [stdout] 1143 | | /// [INFO] [stdout] 1144 | | /// [`NcName`] corresponds to a (restricted) [`String`]. For a [`str`]-like [INFO] [stdout] ... | [INFO] [stdout] 1177 | | pub struct NcNameStr(str); [INFO] [stdout] 1178 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:353:10 [INFO] [stdout] | [INFO] [stdout] 352 | unsafe fn from_auto_unchecked(s: CompactString) -> Self { [INFO] [stdout] | ---------------- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 353 | Self(s.into()) [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 1141 | / rxml_custom_string_type_pair! { [INFO] [stdout] 1142 | | /// String which conforms to the NcName production of Namespaces in XML 1.0. [INFO] [stdout] 1143 | | /// [INFO] [stdout] 1144 | | /// [`NcName`] corresponds to a (restricted) [`String`]. For a [`str`]-like [INFO] [stdout] ... | [INFO] [stdout] 1177 | | pub struct NcNameStr(str); [INFO] [stdout] 1178 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:366:10 [INFO] [stdout] | [INFO] [stdout] 365 | pub unsafe fn from_compact_str_unchecked>(s: T) -> Self { [INFO] [stdout] | ---- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 366 | Self(s.into().into()) [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 1141 | / rxml_custom_string_type_pair! { [INFO] [stdout] 1142 | | /// String which conforms to the NcName production of Namespaces in XML 1.0. [INFO] [stdout] 1143 | | /// [INFO] [stdout] 1144 | | /// [`NcName`] corresponds to a (restricted) [`String`]. For a [`str`]-like [INFO] [stdout] ... | [INFO] [stdout] 1177 | | pub struct NcNameStr(str); [INFO] [stdout] 1178 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:537:8 [INFO] [stdout] | [INFO] [stdout] 535 | fn try_from(other: CompactString) -> Result { [INFO] [stdout] | -------------------- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 536 | $check(&other)?; [INFO] [stdout] 537 | Ok($name(other.into())) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 1141 | / rxml_custom_string_type_pair! { [INFO] [stdout] 1142 | | /// String which conforms to the NcName production of Namespaces in XML 1.0. [INFO] [stdout] 1143 | | /// [INFO] [stdout] 1144 | | /// [`NcName`] corresponds to a (restricted) [`String`]. For a [`str`]-like [INFO] [stdout] ... | [INFO] [stdout] 1177 | | pub struct NcNameStr(str); [INFO] [stdout] 1178 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:595:19 [INFO] [stdout] | [INFO] [stdout] 594 | fn extend>(&mut self, iter: I) { [INFO] [stdout] | ------- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 595 | self.0.extend(iter.into_iter().map(|x| &x.0)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 1141 | / rxml_custom_string_type_pair! { [INFO] [stdout] 1142 | | /// String which conforms to the NcName production of Namespaces in XML 1.0. [INFO] [stdout] 1143 | | /// [INFO] [stdout] 1144 | | /// [`NcName`] corresponds to a (restricted) [`String`]. For a [`str`]-like [INFO] [stdout] ... | [INFO] [stdout] 1177 | | pub struct NcNameStr(str); [INFO] [stdout] 1178 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/strings.rs:617:19 [INFO] [stdout] | [INFO] [stdout] 616 | fn extend>(&mut self, iter: I) { [INFO] [stdout] | ------- these values have significant drop implementation and will observe changes in drop order under Edition 2024 [INFO] [stdout] 617 | self.0.extend(iter.into_iter().map(|x| x.0)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 1141 | / rxml_custom_string_type_pair! { [INFO] [stdout] 1142 | | /// String which conforms to the NcName production of Namespaces in XML 1.0. [INFO] [stdout] 1143 | | /// [INFO] [stdout] 1144 | | /// [`NcName`] corresponds to a (restricted) [`String`]. For a [`str`]-like [INFO] [stdout] ... | [INFO] [stdout] 1177 | | pub struct NcNameStr(str); [INFO] [stdout] 1178 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #123739 [INFO] [stdout] = note: this error originates in the macro `rxml_custom_string_type` which comes from the expansion of the macro `rxml_custom_string_type_pair` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: aborting due to 15 previous errors [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `rxml_validation` (lib test) due to 16 previous errors [INFO] running `Command { std: "docker" "inspect" "d20283282f9fb6fa327931bc627a9b073b3f28a22cc47d8ce6fa976da941e7cd", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "d20283282f9fb6fa327931bc627a9b073b3f28a22cc47d8ce6fa976da941e7cd", kill_on_drop: false }` [INFO] [stdout] d20283282f9fb6fa327931bc627a9b073b3f28a22cc47d8ce6fa976da941e7cd