Kristoffer Carlsson
Kristoffer Carlsson
If this was only in SparseArrays I would blame https://github.com/JuliaLang/julia/issues/54464 but https://github.com/JuliaLang/julia/issues/52137 (as already have been said) seem to exclude this from being a SparseArray specific issue.
Ref https://github.com/JuliaLang/julia/issues/52137#issuecomment-2139411363 for a bisect.
My guess is that this has something to do with the (in my opinion) non ideal implementation of disabling getindex.
> Should this be fixed soon, possibly removing the method/making it more specific not to cause ambiguity? If you can fix this in a good way doing this it would...
I think this is a duplicated of https://github.com/JuliaSparse/SparseArrays.jl/issues/99 which have been fixed by https://github.com/JuliaSparse/SparseArrays.jl/pull/100. I don't know what Julia versions that fix is in though.
I saw it in this log: https://s3.amazonaws.com/julialang-reports/nanosoldier/pkgeval/by_hash/bdc7fb7_vs_bd47eca/Accessors.primary.log
Does any other language use distributed contributing?
There's been a discussion that the current one is not allowed so add back this one which is faster than the slow one but doesn't include an "arena". All of...
`allocate` heavily suggests that the thing is "non-initialized" and has to be further "processed". So that might make sense in this case.
I am a bit uneasy about the HeapAllocator stuff. While I understand it was fun to write is there really no way whatever this is used for that cannot be...