Update openblas-src to 0.10

[maoe]

No description provided.

[IvanUkhov]

Thank you. Would you be able to update lapack-src too?

[bluss]

Hi. Just a question (don't want to stop anything). Is there a reason openblas-src is getting bumps in the 0.x version? This causes incompatible version number upgrades in blas-src and those that depend on blas-src (causing incompatible version bumps further downstream). Is this a necessary bump - or could openblas-src for example avoid using the version number 0.11 for a long time?

Will you release blas-src with a bumped version soon (question)? If so I want to coordinate and wait with ndarray 0.15 just a day or two so that we're up to date with you. Thanks 🙂

[IvanUkhov]

@termoshtt, what is your opinion on the versioning of openblas-src?

[termoshtt]

In my understanding, we keep the minor version (0.10) unless as far as features in Cargo.toml and ABI of BLAS and LAPACK are kept. 0.10.2 includes large changes around the Fortran compiler detection sneaking blas-lapack-rs/openblas-src#47 , but it only bump up patch version.

[bluss]

Thanks for the info. I guess I was also ignorant of what goes into the openblas-src releases 🙂 Nice job. Maybe it would be possible for blas-src to match with several openblas-src versions? I don't know if that can be practical.

[maoe]

Would you be able to update lapack-src too?

Sure, will do.

[maoe]

Done blas-lapack-rs/lapack-src#5

[maoe]

BTW, current version of blas-src is compatible with openblas-src 0.9 and 0.10. So technically speaking it should be possible to specify >= 0.9, < 0.11, which is a common practice in the Haskell community to support a wider range of dependencies. But as far as I can see it's rare to see this kind of version bounds in the Rust community. Why is that?

[bluss]

@maoe I think the reason is that cargo will always pick the newest version. One could imagine cargo trying to pick the "best" version in that range to get all crates in a project to build, but it doesn't do that, if I understand correctly.

[maoe]

Ah I see. Haskell's cabal tries to solve the version constraints then pick the latest versions (this is what you called the "best", I think) amongst the possible solutions.

[IvanUkhov]

Thank you!