Kristoffer Carlsson
Kristoffer Carlsson
https://www.intel.com/content/www/us/en/developer/articles/technical/pardiso-tips.html also has it documented as: > Single and double precision: Starting version 10.2 Intel® oneAPI Math Kernel Library (oneMKL) supports computations in single precision as well as double precision....
> I guess the difference is just between Fortran and C indexing? Makes sense.
I think this is fixed by https://github.com/JuliaSparse/Pardiso.jl/pull/108.
Might be related to https://github.com/JuliaLang/Pkg.jl/issues/4086.
It wasn't the case that you could change rev / repo / path without a corresponding Pkg command so there are some cases (like in `resolve`) where this causes Pkg...
The project hash not updating seems to be due to https://github.com/JuliaLang/Pkg.jl/blob/d2c81dbe7288e9cf6acea2098a2f3de22e24782a/src/Types.jl#L601-L602 where it claims that only compact + deps affect resolve (which is no longer true with sources).
We do not enter the repo handling here: https://github.com/JuliaLang/Pkg.jl/blob/d2c81dbe7288e9cf6acea2098a2f3de22e24782a/src/Operations.jl#L410-L418 because we see that we have already downloaded the package with the tree hash recorded in the manifest (failing to see...
Any suggestions of what these should say?
Should imo be a part of Pkg.gc since that already handles artifacts and packages.
I would have think this is already the case from the existing code? Do you have something like an MWE where it isn't? ``` julia> Base.active_project() "/home/kc/JuliaPkgs/PackageCompiler.jl/examples/MyLib/build/Project.toml" julia> project =...