[INFO] fetching crate cpython 0.7.2... [INFO] checking cpython-0.7.2 against try#c387b04bf028733cd561d62128c8a5eee4bc1458+rustflags=-Dtail_expr_drop_order for pr-130930 [INFO] extracting crate cpython 0.7.2 into /workspace/builds/worker-4-tc2/source [INFO] validating manifest of crates.io crate cpython 0.7.2 on toolchain c387b04bf028733cd561d62128c8a5eee4bc1458 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+c387b04bf028733cd561d62128c8a5eee4bc1458" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] started tweaking crates.io crate cpython 0.7.2 [INFO] finished tweaking crates.io crate cpython 0.7.2 [INFO] tweaked toml for crates.io crate cpython 0.7.2 written to /workspace/builds/worker-4-tc2/source/Cargo.toml [INFO] crate crates.io crate cpython 0.7.2 already has a lockfile, it will not be regenerated [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+c387b04bf028733cd561d62128c8a5eee4bc1458" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-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:6252d7ea7fb8caaf7af6d800c5fb250a9cd862b9a7f9508afb3c54fa7fe1102e" "/opt/rustwide/cargo-home/bin/cargo" "+c387b04bf028733cd561d62128c8a5eee4bc1458" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 1419a56a95ca8f952871be19e02386dfe652de6bd817c47a9c03514549d90cac [INFO] running `Command { std: "docker" "start" "-a" "1419a56a95ca8f952871be19e02386dfe652de6bd817c47a9c03514549d90cac", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "1419a56a95ca8f952871be19e02386dfe652de6bd817c47a9c03514549d90cac", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "1419a56a95ca8f952871be19e02386dfe652de6bd817c47a9c03514549d90cac", kill_on_drop: false }` [INFO] [stdout] 1419a56a95ca8f952871be19e02386dfe652de6bd817c47a9c03514549d90cac [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-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:6252d7ea7fb8caaf7af6d800c5fb250a9cd862b9a7f9508afb3c54fa7fe1102e" "/opt/rustwide/cargo-home/bin/cargo" "+c387b04bf028733cd561d62128c8a5eee4bc1458" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 501bfbf913e5126ba5ddf0e8c0d51e81c0879d96fdd873c112171d9db2de4555 [INFO] running `Command { std: "docker" "start" "-a" "501bfbf913e5126ba5ddf0e8c0d51e81c0879d96fdd873c112171d9db2de4555", kill_on_drop: false }` [INFO] [stderr] Compiling memchr v2.4.1 [INFO] [stderr] Compiling regex-syntax v0.6.27 [INFO] [stderr] Compiling libc v0.2.103 [INFO] [stderr] Compiling serde v1.0.130 [INFO] [stderr] Compiling rustversion v1.0.5 [INFO] [stderr] Compiling cpython v0.7.2 (/opt/rustwide/workdir) [INFO] [stderr] Compiling paste v1.0.5 [INFO] [stderr] Checking half v1.7.1 [INFO] [stderr] Compiling num-traits v0.2.14 [INFO] [stderr] Compiling aho-corasick v0.7.18 [INFO] [stderr] Compiling regex v1.6.0 [INFO] [stderr] Checking serde_bytes v0.11.5 [INFO] [stderr] Checking serde_cbor v0.11.2 [INFO] [stderr] Compiling python3-sys v0.7.2 [INFO] [stdout] error: this value of type `Result<&T, PyErr>` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/conversion.rs:146:15 [INFO] [stdout] | [INFO] [stdout] 142 | fn with_extracted(py: Python, obj: &PyObject, f: F) -> PyResult [INFO] [stdout] | - these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] ... [INFO] [stdout] 146 | match FromPyObject::extract(py, obj) { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [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] [INFO] [stdout] [INFO] [stdout] error: this value of type `object::PyObject` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objectprotocol.rs:250:9 [INFO] [stdout] | [INFO] [stdout] 244 | args: A, [INFO] [stdout] | ---- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] ... [INFO] [stdout] 250 | self.getattr(py, name)?.call(py, args, kwargs) [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: this value of type `Result<&T, PyErr>` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/conversion.rs:146:15 [INFO] [stdout] | [INFO] [stdout] 142 | fn with_extracted(py: Python, obj: &PyObject, f: F) -> PyResult [INFO] [stdout] | - these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] ... [INFO] [stdout] 146 | match FromPyObject::extract(py, obj) { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [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] [INFO] [stdout] [INFO] [stdout] error: this value of type `object::PyObject` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objects/module.rs:136:9 [INFO] [stdout] | [INFO] [stdout] 130 | args: A, [INFO] [stdout] | ---- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] ... [INFO] [stdout] 136 | self.as_object().getattr(py, name)?.call(py, args, kwargs) [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: this value of type `object::PyObject` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objectprotocol.rs:250:9 [INFO] [stdout] | [INFO] [stdout] 244 | args: A, [INFO] [stdout] | ---- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] ... [INFO] [stdout] 250 | self.getattr(py, name)?.call(py, args, kwargs) [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: this value of type `[object::PyObject; 1]` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objects/tuple.rs:120:31 [INFO] [stdout] | [INFO] [stdout] 119 | fn into_py_object(self, py: Python) -> PyTuple { [INFO] [stdout] | ---- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] 120 | PyTuple::new(py, &[ [INFO] [stdout] | _______________________________^ [INFO] [stdout] 121 | | $(py_coerce_expr!(self.$n.into_py_object(py)).into_object(),)+ [INFO] [stdout] 122 | | ]) [INFO] [stdout] | |_____________^ [INFO] [stdout] ... [INFO] [stdout] 145 | tuple_conversion!(1, (ref0, 0, A)); [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 `tuple_conversion` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: this value of type `[object::PyObject; 2]` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objects/tuple.rs:120:31 [INFO] [stdout] | [INFO] [stdout] 119 | fn into_py_object(self, py: Python) -> PyTuple { [INFO] [stdout] | ---- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] 120 | PyTuple::new(py, &[ [INFO] [stdout] | _______________________________^ [INFO] [stdout] 121 | | $(py_coerce_expr!(self.$n.into_py_object(py)).into_object(),)+ [INFO] [stdout] 122 | | ]) [INFO] [stdout] | |_____________^ [INFO] [stdout] ... [INFO] [stdout] 146 | tuple_conversion!(2, (ref0, 0, A), (ref1, 1, B)); [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 `tuple_conversion` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: this value of type `[object::PyObject; 3]` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objects/tuple.rs:120:31 [INFO] [stdout] | [INFO] [stdout] 119 | fn into_py_object(self, py: Python) -> PyTuple { [INFO] [stdout] | ---- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] 120 | PyTuple::new(py, &[ [INFO] [stdout] | _______________________________^ [INFO] [stdout] 121 | | $(py_coerce_expr!(self.$n.into_py_object(py)).into_object(),)+ [INFO] [stdout] 122 | | ]) [INFO] [stdout] | |_____________^ [INFO] [stdout] ... [INFO] [stdout] 147 | tuple_conversion!(3, (ref0, 0, A), (ref1, 1, B), (ref2, 2, C)); [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 `tuple_conversion` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: this value of type `[object::PyObject; 4]` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objects/tuple.rs:120:31 [INFO] [stdout] | [INFO] [stdout] 119 | fn into_py_object(self, py: Python) -> PyTuple { [INFO] [stdout] | ---- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] 120 | PyTuple::new(py, &[ [INFO] [stdout] | _______________________________^ [INFO] [stdout] 121 | | $(py_coerce_expr!(self.$n.into_py_object(py)).into_object(),)+ [INFO] [stdout] 122 | | ]) [INFO] [stdout] | |_____________^ [INFO] [stdout] ... [INFO] [stdout] 148 | tuple_conversion!(4, (ref0, 0, A), (ref1, 1, B), (ref2, 2, C), (ref3, 3, D)); [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 `tuple_conversion` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: this value of type `[object::PyObject; 5]` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objects/tuple.rs:120:31 [INFO] [stdout] | [INFO] [stdout] 119 | fn into_py_object(self, py: Python) -> PyTuple { [INFO] [stdout] | ---- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] 120 | PyTuple::new(py, &[ [INFO] [stdout] | _______________________________^ [INFO] [stdout] 121 | | $(py_coerce_expr!(self.$n.into_py_object(py)).into_object(),)+ [INFO] [stdout] 122 | | ]) [INFO] [stdout] | |_____________^ [INFO] [stdout] ... [INFO] [stdout] 149 | / tuple_conversion!( [INFO] [stdout] 150 | | 5, [INFO] [stdout] 151 | | (ref0, 0, A), [INFO] [stdout] 152 | | (ref1, 1, B), [INFO] [stdout] ... | [INFO] [stdout] 155 | | (ref4, 4, E) [INFO] [stdout] 156 | | ); [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 `tuple_conversion` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: this value of type `[object::PyObject; 6]` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objects/tuple.rs:120:31 [INFO] [stdout] | [INFO] [stdout] 119 | fn into_py_object(self, py: Python) -> PyTuple { [INFO] [stdout] | ---- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] 120 | PyTuple::new(py, &[ [INFO] [stdout] | _______________________________^ [INFO] [stdout] 121 | | $(py_coerce_expr!(self.$n.into_py_object(py)).into_object(),)+ [INFO] [stdout] 122 | | ]) [INFO] [stdout] | |_____________^ [INFO] [stdout] ... [INFO] [stdout] 157 | / tuple_conversion!( [INFO] [stdout] 158 | | 6, [INFO] [stdout] 159 | | (ref0, 0, A), [INFO] [stdout] 160 | | (ref1, 1, B), [INFO] [stdout] ... | [INFO] [stdout] 164 | | (ref5, 5, F) [INFO] [stdout] 165 | | ); [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 `tuple_conversion` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: this value of type `[object::PyObject; 7]` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objects/tuple.rs:120:31 [INFO] [stdout] | [INFO] [stdout] 119 | fn into_py_object(self, py: Python) -> PyTuple { [INFO] [stdout] | ---- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] 120 | PyTuple::new(py, &[ [INFO] [stdout] | _______________________________^ [INFO] [stdout] 121 | | $(py_coerce_expr!(self.$n.into_py_object(py)).into_object(),)+ [INFO] [stdout] 122 | | ]) [INFO] [stdout] | |_____________^ [INFO] [stdout] ... [INFO] [stdout] 166 | / tuple_conversion!( [INFO] [stdout] 167 | | 7, [INFO] [stdout] 168 | | (ref0, 0, A), [INFO] [stdout] 169 | | (ref1, 1, B), [INFO] [stdout] ... | [INFO] [stdout] 174 | | (ref6, 6, G) [INFO] [stdout] 175 | | ); [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 `tuple_conversion` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: this value of type `[object::PyObject; 8]` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objects/tuple.rs:120:31 [INFO] [stdout] | [INFO] [stdout] 119 | fn into_py_object(self, py: Python) -> PyTuple { [INFO] [stdout] | ---- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] 120 | PyTuple::new(py, &[ [INFO] [stdout] | _______________________________^ [INFO] [stdout] 121 | | $(py_coerce_expr!(self.$n.into_py_object(py)).into_object(),)+ [INFO] [stdout] 122 | | ]) [INFO] [stdout] | |_____________^ [INFO] [stdout] ... [INFO] [stdout] 176 | / tuple_conversion!( [INFO] [stdout] 177 | | 8, [INFO] [stdout] 178 | | (ref0, 0, A), [INFO] [stdout] 179 | | (ref1, 1, B), [INFO] [stdout] ... | [INFO] [stdout] 185 | | (ref7, 7, H) [INFO] [stdout] 186 | | ); [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 `tuple_conversion` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: this value of type `[object::PyObject; 9]` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objects/tuple.rs:120:31 [INFO] [stdout] | [INFO] [stdout] 119 | fn into_py_object(self, py: Python) -> PyTuple { [INFO] [stdout] | ---- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] 120 | PyTuple::new(py, &[ [INFO] [stdout] | _______________________________^ [INFO] [stdout] 121 | | $(py_coerce_expr!(self.$n.into_py_object(py)).into_object(),)+ [INFO] [stdout] 122 | | ]) [INFO] [stdout] | |_____________^ [INFO] [stdout] ... [INFO] [stdout] 187 | / tuple_conversion!( [INFO] [stdout] 188 | | 9, [INFO] [stdout] 189 | | (ref0, 0, A), [INFO] [stdout] 190 | | (ref1, 1, B), [INFO] [stdout] ... | [INFO] [stdout] 197 | | (ref8, 8, I) [INFO] [stdout] 198 | | ); [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 `tuple_conversion` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/boolobject.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | pyobject_newtype!(PyBool, PyBool_Check, PyBool_Type); [INFO] [stdout] | ---------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: `#[warn(static_mut_refs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/capsule.rs:190:1 [INFO] [stdout] | [INFO] [stdout] 190 | pyobject_newtype!(PyCapsule, PyCapsule_CheckExact, PyCapsule_Type); [INFO] [stdout] | ------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/dict.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | pyobject_newtype!(PyDict, PyDict_Check, PyDict_Type); [INFO] [stdout] | ---------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/list.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | pyobject_newtype!(PyList, PyList_Check, PyList_Type); [INFO] [stdout] | ---------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/module.rs:33:1 [INFO] [stdout] | [INFO] [stdout] 33 | pyobject_newtype!(PyModule, PyModule_Check, PyModule_Type); [INFO] [stdout] | ---------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/num.rs:56:1 [INFO] [stdout] | [INFO] [stdout] 56 | pyobject_newtype!(PyLong, PyLong_Check, PyLong_Type); [INFO] [stdout] | ---------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/num.rs:65:1 [INFO] [stdout] | [INFO] [stdout] 65 | pyobject_newtype!(PyFloat, PyFloat_Check, PyFloat_Type); [INFO] [stdout] | ------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/object.rs:113:44 [INFO] [stdout] | [INFO] [stdout] 113 | unsafe { PyType::from_type_ptr(py, &mut ffi::PyBaseObject_Type) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] help: use `&raw mut` instead to create a raw pointer [INFO] [stdout] | [INFO] [stdout] 113 | unsafe { PyType::from_type_ptr(py, &raw mut ffi::PyBaseObject_Type) } [INFO] [stdout] | ~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/set.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | pyobject_newtype!(PySet, PySet_Check, PySet_Type); [INFO] [stdout] | ------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/string.rs:36:1 [INFO] [stdout] | [INFO] [stdout] 36 | pyobject_newtype!(PyString, PyUnicode_Check, PyUnicode_Type); [INFO] [stdout] | ------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/string.rs:42:1 [INFO] [stdout] | [INFO] [stdout] 42 | pyobject_newtype!(PyBytes, PyBytes_Check, PyBytes_Type); [INFO] [stdout] | ------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/tuple.rs:31:1 [INFO] [stdout] | [INFO] [stdout] 31 | pyobject_newtype!(PyTuple, PyTuple_Check, PyTuple_Type); [INFO] [stdout] | ------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/typeobject.rs:31:1 [INFO] [stdout] | [INFO] [stdout] 31 | pyobject_newtype!(PyType, PyType_Check, PyType_Type); [INFO] [stdout] | ---------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: aborting due to 12 previous errors; 13 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `cpython` (lib) due to 13 previous errors; 13 warnings emitted [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] [stdout] error: this value of type `object::PyObject` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objects/module.rs:136:9 [INFO] [stdout] | [INFO] [stdout] 130 | args: A, [INFO] [stdout] | ---- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] ... [INFO] [stdout] 136 | self.as_object().getattr(py, name)?.call(py, args, kwargs) [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: this value of type `Zip, std::vec::IntoIter>` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objects/sequence.rs:523:25 [INFO] [stdout] | [INFO] [stdout] 508 | let gil = Python::acquire_gil(); [INFO] [stdout] | --- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] ... [INFO] [stdout] 511 | let seq = v [INFO] [stdout] | --- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] ... [INFO] [stdout] 516 | let concat_seq = seq [INFO] [stdout] | ---------- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] ... [INFO] [stdout] 523 | for (el, cc) in seq.iter(py).unwrap().zip(concat_v) { [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: this value of type `Zip, std::slice::Iter<'_, &str>>` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objects/sequence.rs:567:26 [INFO] [stdout] | [INFO] [stdout] 552 | let gil = Python::acquire_gil(); [INFO] [stdout] | --- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] ... [INFO] [stdout] 555 | let seq = v [INFO] [stdout] | --- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] ... [INFO] [stdout] 560 | let repeat_seq = seq [INFO] [stdout] | ---------- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] ... [INFO] [stdout] 567 | for (el, rpt) in seq.iter(py).unwrap().zip(repeated.iter()) { [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: this value of type `[object::PyObject; 1]` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objects/tuple.rs:120:31 [INFO] [stdout] | [INFO] [stdout] 119 | fn into_py_object(self, py: Python) -> PyTuple { [INFO] [stdout] | ---- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] 120 | PyTuple::new(py, &[ [INFO] [stdout] | _______________________________^ [INFO] [stdout] 121 | | $(py_coerce_expr!(self.$n.into_py_object(py)).into_object(),)+ [INFO] [stdout] 122 | | ]) [INFO] [stdout] | |_____________^ [INFO] [stdout] ... [INFO] [stdout] 145 | tuple_conversion!(1, (ref0, 0, A)); [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 `tuple_conversion` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: this value of type `[object::PyObject; 2]` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objects/tuple.rs:120:31 [INFO] [stdout] | [INFO] [stdout] 119 | fn into_py_object(self, py: Python) -> PyTuple { [INFO] [stdout] | ---- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] 120 | PyTuple::new(py, &[ [INFO] [stdout] | _______________________________^ [INFO] [stdout] 121 | | $(py_coerce_expr!(self.$n.into_py_object(py)).into_object(),)+ [INFO] [stdout] 122 | | ]) [INFO] [stdout] | |_____________^ [INFO] [stdout] ... [INFO] [stdout] 146 | tuple_conversion!(2, (ref0, 0, A), (ref1, 1, B)); [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 `tuple_conversion` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: this value of type `[object::PyObject; 3]` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objects/tuple.rs:120:31 [INFO] [stdout] | [INFO] [stdout] 119 | fn into_py_object(self, py: Python) -> PyTuple { [INFO] [stdout] | ---- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] 120 | PyTuple::new(py, &[ [INFO] [stdout] | _______________________________^ [INFO] [stdout] 121 | | $(py_coerce_expr!(self.$n.into_py_object(py)).into_object(),)+ [INFO] [stdout] 122 | | ]) [INFO] [stdout] | |_____________^ [INFO] [stdout] ... [INFO] [stdout] 147 | tuple_conversion!(3, (ref0, 0, A), (ref1, 1, B), (ref2, 2, C)); [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 `tuple_conversion` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: this value of type `[object::PyObject; 4]` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objects/tuple.rs:120:31 [INFO] [stdout] | [INFO] [stdout] 119 | fn into_py_object(self, py: Python) -> PyTuple { [INFO] [stdout] | ---- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] 120 | PyTuple::new(py, &[ [INFO] [stdout] | _______________________________^ [INFO] [stdout] 121 | | $(py_coerce_expr!(self.$n.into_py_object(py)).into_object(),)+ [INFO] [stdout] 122 | | ]) [INFO] [stdout] | |_____________^ [INFO] [stdout] ... [INFO] [stdout] 148 | tuple_conversion!(4, (ref0, 0, A), (ref1, 1, B), (ref2, 2, C), (ref3, 3, D)); [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 `tuple_conversion` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: this value of type `[object::PyObject; 5]` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objects/tuple.rs:120:31 [INFO] [stdout] | [INFO] [stdout] 119 | fn into_py_object(self, py: Python) -> PyTuple { [INFO] [stdout] | ---- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] 120 | PyTuple::new(py, &[ [INFO] [stdout] | _______________________________^ [INFO] [stdout] 121 | | $(py_coerce_expr!(self.$n.into_py_object(py)).into_object(),)+ [INFO] [stdout] 122 | | ]) [INFO] [stdout] | |_____________^ [INFO] [stdout] ... [INFO] [stdout] 149 | / tuple_conversion!( [INFO] [stdout] 150 | | 5, [INFO] [stdout] 151 | | (ref0, 0, A), [INFO] [stdout] 152 | | (ref1, 1, B), [INFO] [stdout] ... | [INFO] [stdout] 155 | | (ref4, 4, E) [INFO] [stdout] 156 | | ); [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 `tuple_conversion` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: this value of type `[object::PyObject; 6]` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objects/tuple.rs:120:31 [INFO] [stdout] | [INFO] [stdout] 119 | fn into_py_object(self, py: Python) -> PyTuple { [INFO] [stdout] | ---- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] 120 | PyTuple::new(py, &[ [INFO] [stdout] | _______________________________^ [INFO] [stdout] 121 | | $(py_coerce_expr!(self.$n.into_py_object(py)).into_object(),)+ [INFO] [stdout] 122 | | ]) [INFO] [stdout] | |_____________^ [INFO] [stdout] ... [INFO] [stdout] 157 | / tuple_conversion!( [INFO] [stdout] 158 | | 6, [INFO] [stdout] 159 | | (ref0, 0, A), [INFO] [stdout] 160 | | (ref1, 1, B), [INFO] [stdout] ... | [INFO] [stdout] 164 | | (ref5, 5, F) [INFO] [stdout] 165 | | ); [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 `tuple_conversion` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: this value of type `[object::PyObject; 7]` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objects/tuple.rs:120:31 [INFO] [stdout] | [INFO] [stdout] 119 | fn into_py_object(self, py: Python) -> PyTuple { [INFO] [stdout] | ---- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] 120 | PyTuple::new(py, &[ [INFO] [stdout] | _______________________________^ [INFO] [stdout] 121 | | $(py_coerce_expr!(self.$n.into_py_object(py)).into_object(),)+ [INFO] [stdout] 122 | | ]) [INFO] [stdout] | |_____________^ [INFO] [stdout] ... [INFO] [stdout] 166 | / tuple_conversion!( [INFO] [stdout] 167 | | 7, [INFO] [stdout] 168 | | (ref0, 0, A), [INFO] [stdout] 169 | | (ref1, 1, B), [INFO] [stdout] ... | [INFO] [stdout] 174 | | (ref6, 6, G) [INFO] [stdout] 175 | | ); [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 `tuple_conversion` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: this value of type `[object::PyObject; 8]` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objects/tuple.rs:120:31 [INFO] [stdout] | [INFO] [stdout] 119 | fn into_py_object(self, py: Python) -> PyTuple { [INFO] [stdout] | ---- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] 120 | PyTuple::new(py, &[ [INFO] [stdout] | _______________________________^ [INFO] [stdout] 121 | | $(py_coerce_expr!(self.$n.into_py_object(py)).into_object(),)+ [INFO] [stdout] 122 | | ]) [INFO] [stdout] | |_____________^ [INFO] [stdout] ... [INFO] [stdout] 176 | / tuple_conversion!( [INFO] [stdout] 177 | | 8, [INFO] [stdout] 178 | | (ref0, 0, A), [INFO] [stdout] 179 | | (ref1, 1, B), [INFO] [stdout] ... | [INFO] [stdout] 185 | | (ref7, 7, H) [INFO] [stdout] 186 | | ); [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 `tuple_conversion` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: this value of type `[object::PyObject; 9]` has significant drop implementation that will have a different drop order from that of Edition 2021 [INFO] [stdout] --> src/objects/tuple.rs:120:31 [INFO] [stdout] | [INFO] [stdout] 119 | fn into_py_object(self, py: Python) -> PyTuple { [INFO] [stdout] | ---- these local bindings with significant drop implementation may observe changes in drop order under Edition 2024 [INFO] [stdout] 120 | PyTuple::new(py, &[ [INFO] [stdout] | _______________________________^ [INFO] [stdout] 121 | | $(py_coerce_expr!(self.$n.into_py_object(py)).into_object(),)+ [INFO] [stdout] 122 | | ]) [INFO] [stdout] | |_____________^ [INFO] [stdout] ... [INFO] [stdout] 187 | / tuple_conversion!( [INFO] [stdout] 188 | | 9, [INFO] [stdout] 189 | | (ref0, 0, A), [INFO] [stdout] 190 | | (ref1, 1, B), [INFO] [stdout] ... | [INFO] [stdout] 197 | | (ref8, 8, I) [INFO] [stdout] 198 | | ); [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 `tuple_conversion` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/boolobject.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | pyobject_newtype!(PyBool, PyBool_Check, PyBool_Type); [INFO] [stdout] | ---------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: `#[warn(static_mut_refs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/capsule.rs:190:1 [INFO] [stdout] | [INFO] [stdout] 190 | pyobject_newtype!(PyCapsule, PyCapsule_CheckExact, PyCapsule_Type); [INFO] [stdout] | ------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/dict.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | pyobject_newtype!(PyDict, PyDict_Check, PyDict_Type); [INFO] [stdout] | ---------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/list.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | pyobject_newtype!(PyList, PyList_Check, PyList_Type); [INFO] [stdout] | ---------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/module.rs:33:1 [INFO] [stdout] | [INFO] [stdout] 33 | pyobject_newtype!(PyModule, PyModule_Check, PyModule_Type); [INFO] [stdout] | ---------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/num.rs:56:1 [INFO] [stdout] | [INFO] [stdout] 56 | pyobject_newtype!(PyLong, PyLong_Check, PyLong_Type); [INFO] [stdout] | ---------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/num.rs:65:1 [INFO] [stdout] | [INFO] [stdout] 65 | pyobject_newtype!(PyFloat, PyFloat_Check, PyFloat_Type); [INFO] [stdout] | ------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/object.rs:113:44 [INFO] [stdout] | [INFO] [stdout] 113 | unsafe { PyType::from_type_ptr(py, &mut ffi::PyBaseObject_Type) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] help: use `&raw mut` instead to create a raw pointer [INFO] [stdout] | [INFO] [stdout] 113 | unsafe { PyType::from_type_ptr(py, &raw mut ffi::PyBaseObject_Type) } [INFO] [stdout] | ~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/set.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | pyobject_newtype!(PySet, PySet_Check, PySet_Type); [INFO] [stdout] | ------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/string.rs:36:1 [INFO] [stdout] | [INFO] [stdout] 36 | pyobject_newtype!(PyString, PyUnicode_Check, PyUnicode_Type); [INFO] [stdout] | ------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/string.rs:42:1 [INFO] [stdout] | [INFO] [stdout] 42 | pyobject_newtype!(PyBytes, PyBytes_Check, PyBytes_Type); [INFO] [stdout] | ------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/tuple.rs:31:1 [INFO] [stdout] | [INFO] [stdout] 31 | pyobject_newtype!(PyTuple, PyTuple_Check, PyTuple_Type); [INFO] [stdout] | ------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged [INFO] [stdout] --> src/objects/mod.rs:119:85 [INFO] [stdout] | [INFO] [stdout] 119 | unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] ::: src/objects/typeobject.rs:31:1 [INFO] [stdout] | [INFO] [stdout] 31 | pyobject_newtype!(PyType, PyType_Check, PyType_Type); [INFO] [stdout] | ---------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: aborting due to 14 previous errors; 13 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `cpython` (lib test) due to 15 previous errors; 13 warnings emitted [INFO] running `Command { std: "docker" "inspect" "501bfbf913e5126ba5ddf0e8c0d51e81c0879d96fdd873c112171d9db2de4555", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "501bfbf913e5126ba5ddf0e8c0d51e81c0879d96fdd873c112171d9db2de4555", kill_on_drop: false }` [INFO] [stdout] 501bfbf913e5126ba5ddf0e8c0d51e81c0879d96fdd873c112171d9db2de4555