Bump ndarray from 0.16.1 to 0.17.2 in /moors

[dependabot]

Bumps ndarray from 0.16.1 to 0.17.2.

Changelog

Sourced from ndarray's changelog.

Version 0.17.2 (2026-01-10)

Version 0.17.2 is mainly a patch fix to bugs related to the new ArrayRef implementation.

In addition, ndarray has reduced its packaging footprint to ease supply chain reviews (and shrink the binary size!). A special thanks to @​SwishSwushPow and @​weiznich for bringing this to our attention and making the necessary changes.

Added

• Add type aliases for higher-dimensional ArcArrays by @​varchasgopalaswamy #1561

Fixed

• Add PartialEq implementations between ArrayRef and ArrayBase by @​akern40 #1557
• Implement Sync for ArrayParts by @​gaumut #1552

Documentation

• fix some typos in comments by @​tinyfoolish #1547

Version 0.17.1 (2025-11-02)

Version 0.17.1 provides a patch to fix the originally-unsound implementation of the new array reference types.

The reference types are now all unsized. Practically speaking, this has one major implication: writing functions and traits that accept RawRef and LayoutRef will now need a + ?Sized bound to work ergonomically with ArrayRef. For example, the release notes for 0.17.0 said

Reading / Writing Shape: LayoutRef<A, D>

LayoutRef lets functions view or modify shape/stride information without touching data. This replaces verbose signatures like:

fn alter_view<S>(a: &mut ArrayBase<S, Ix1>)
where S: Data<Elem = f64>;

Use AsRef / AsMut for best compatibility:

fn alter_shape<T>(a: &mut T)
where T: AsMut<LayoutRef<f64>>;

However, these functions now need an additional bound to allow for callers to pass in &ArrayRef types:

fn alter_shape<T>(a: &mut T)
where T: AsMut<LayoutRef<f64>> + ?Sized; // Added bound here

A huge thank you to Sarah Quiñones (@​sarah-quinones) for catching the original unsound bug and helping to fix it. She does truly excellent work with faer-rs; check it out!

Version 0.17.0 (2025-10-14) [YANKED]

... (truncated)

Commits

• 2cf23d6 chore: Release
• 1eb4559 Remove most version specifiers in README (#1573)
• 59c1ce0 Craft a release log for 0.17.2 (#1572)
• 6fd0a9d Clean up clippy allows and unnecessary borrows (#1571)
• 8adf5d8 Revert #1563 and #1567 to prepare for patch release (#1570)
• 953f2e9 Move LayoutBitset to its own module (#1567)
• 6e02f15 Configure docs for feature gates globally (#1565)
• d573745 Rename Layout to LayoutBitset (#1563)
• 13a8963 Add PartialEq implementations between ArrayRef and ArrayBase (#1557)
• e039158 Add additional commits to ignore on git blame (#1562)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.26%. Comparing base (9e7a482) to head (896e300).
⚠️ Report is 11 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #279      +/-   ##
==========================================
- Coverage   94.84%   94.26%   -0.59%     
==========================================
  Files          80       18      -62     
  Lines        5707     1098    -4609     
==========================================
- Hits         5413     1035    -4378     
+ Misses        294       63     -231     

Flag	Coverage Δ
moors	?
pymoors	94.26% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[codspeed-hq]

Merging this PR will improve performance by 12.18%

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

⚡ 3 improved benchmarks
✅ 3 untouched benchmarks
⏩ 3 skipped benchmarks¹

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
⚡	WallTime	test_compare_scipy_cdist_vs_pymoors[1500]	95.1 ms	85.4 ms	+11.38%
⚡	WallTime	test_compare_scipy_cdist_vs_pymoors[1000]	28.3 ms	25.3 ms	+12.18%
⚡	WallTime	test_compare_scipy_cdist_vs_pymoors[2500]	443.1 ms	399.9 ms	+10.81%

---

_{Comparing dependabot/cargo/moors/ndarray-0.17.2 (896e300) with main (9e7a482)}

Footnotes

1. 3 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩