Skip to content

Conversation

@robfitzgerald
Copy link
Contributor

@robfitzgerald robfitzgerald commented Nov 25, 2025

hey @kylecarow, i think this range dependency isn't what you need here. i just read up and learned that range dependencies need to be supported transitively. so that means that compass also needs to support all ndarray versions in the range [0.15.3, 0.18.0).

this PR instead proposes you use a semver-compatible dependency declaration of ndarray versions matching 0.16.x. so that downstream users of ninterp can also import ndarray versions [0.16.0, 0.16.1] into their crate.

edit: everything i just said but "0.17" instead to match your benchmarking CI

@kylecarow
Copy link
Collaborator

It seems like my attempts to allow any 'actually compatible but not semver compatible' version of ndarray to be used are proving more of a headache for myself and downstream projects than a benefit. It's difficult/impossible to even get crates to unify the dependency if it isn't the latest major version anyway. I will go ahead and accept this PR and merge, thanks!

Resolves #7

@kylecarow kylecarow merged commit 84861d3 into NREL:main Nov 25, 2025
1 check passed
@robfitzgerald robfitzgerald deleted the rjf/fix-ndarray-interop branch November 25, 2025 23:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants