Cross will stop working in Rust 2024 Edition

[sylv256]

Checklist

• I've looked through the issues and pull requests for similar reports

Describe your issue

Cross will stop working in Rust 2024 because it uses an outdated feature.
Please migrate from mutable statics to support the latest Rust edition.

What target(s) are you cross-compiling for?

x86_64-pc-windows-gnu

Which operating system is the host (e.g computer cross is on) running?

• macOS
• Windows
• Linux / BSD
• other OS (specify in description)

What architecture is the host?

• x86_64 / AMD64
• arm32
• arm64 (including Mac M1)

What container engine is cross using?

• docker
• podman
• other container engine (specify in description)

cross version

cross 0.2.5 (ac4c11c 2024-09-24)

Example

Warnings like this are repeated multiple times while compiling.

warning: creating a shared reference to mutable static is discouraged
  --> src/temp.rs:91:8
   |
91 |     Ok(DIRS.last().expect("should not be empty").path())
   |        ^^^^^^^^^^^ shared reference to mutable static
   |
   = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2024/static-mut-references.html>
   = note: shared references to mutable statics are dangerous; it's undefined behavior if the static is mutated or if a mutable reference is created for it while the shared reference lives

Additional information / notes

No response

[Emilgardis]

I dont see how this is an issue, it will not stop working when Rust 2024 is released, we will still be on 2021 edition. When we update to 2024 we will have to move to the alternatives, but right now its fine

[sylv256]

The reason why it's being deprecated is quite important. I'd suggest reading that before deciding it's unnecessary to refactor for now.

[Emilgardis]

Ok, that reason is more compelling. The current implementation shouldnt trigger immediate UB as we've reasoned about it (we do uphold the conditions), but we should change it to not chance it.

[Sewer56]

In some CI setups, running cargo install cross --git https://github.com/cross-rs/cross may fail actually.

Users of the very popular actions-rust-lang/setup-rust-toolchain which is often used transitively in CI setups would experience CI errors, because the action sets -D warnings by default.

I figured I'd give a heads up here.

Edit: In case it's not obvious, you can use RUSTFLAGS="" cargo install cross --git https://github.com/cross-rs/cross (bash) or similar as a temporary workaround.