Closed tbu- closed 2 years ago
Just adding a note. The issue seems to be an old version of num-complex
that ndarray
used to use back in v0.9.1
The crate ndarray
from v0.13.0 (released in sept. 2019) compiles fine also on latest Rust nightly
bisection seems to point to commit 10f4ce324baf7cfb7ce2b2096662b82b79204944 cc @cjgillot
searched nightlies: from nightly-2022-04-01 to nightly-2022-06-28 regressed nightly: nightly-2022-06-23 searched commits: from https://github.com/rust-lang/rust/commit/dc80ca78b6ec2b6bba02560470347433bcd0bb3c to https://github.com/rust-lang/rust/commit/10f4ce324baf7cfb7ce2b2096662b82b79204944 regressed commit: https://github.com/rust-lang/rust/commit/10f4ce324baf7cfb7ce2b2096662b82b79204944
(unsure if this regression may hit other more recent crates)
I've been suspecting this bug for a few days, but unable to reproduce it. I think I have a patch, will confirm once I manage to MCVE.
WG-prioritization assigning priority (Zulip discussion).
@rustbot label -I-prioritize +P-high
ndarray 0.9.1 compiles with rustc 1.61.0 but not with rustc 1.64.0-nightly (2f3ddd9f5 2022-06-27).
Code
Put this into a
Cargo.toml
of a new project:rustc stable <= 1.61.0 compiles the crate fine, rustc nightly gives the following error:
Version it worked on
Version with regression
@rustbot modify labels: +regression-from-stable-to-nightly -regression-untriaged