Alexis Montoison

I checked a little bit and it seems that Metis always need the full graph. The issue with the wrapper `Hermitian` is that both triangles can be also stored so...

Yes, you answered before that I modified my last message. After we can also add a dispatch like that: ```julia Metis.graph(G::Hermitian{

We could do everything with `Hermitian`. In our optimization solver, we just don't wrap the matrix with `Hermitian`, so it was great for us to also have a Julia function...

@alyst I should be able to review the PR next week.

@alyst I have switched to the new API and generated all wrappers in `src/libmklsparse.jl`. This should simplify your PR.

Thanks @alyst !! I will update the token for coverage reports.

> I encountered essentially the same bug. Here is a smaller example that might be helpful: > > ``` > A = sparse([1.0 1.0]); B = [1 0; 0 1.0]...

I find the culprit, MKL.jl is loading an `LP64` interface by default: https://github.com/JuliaLinearAlgebra/MKL.jl/commit/cbbaacd1634f52936e6d0f617a8dde10e9d524b6 It was changed with a recent release of MKL.jl (v6.0). We load an `ILP64` here in MKLSparse.jl:...

@ViralBShah Is it not possible to still load the interface `ILP64` in MKL.jl?

> I thought we use the ILP64 by default in MKL. MKL now has the `_64` suffixes for ILP64 as well. Do you know in which version of Intel MKL...