Conversation
|
I (believe) this implements the idea in #40018 (comment) I really hope it isn't a performance trainwreck edit: |
|
JuliaSparse/SparseArrays.jl#637 would fix the sparsearrays test case looks like there was some previous discussion in #43644 |
|
@nanosoldier |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as duplicate.
This comment was marked as duplicate.
|
The package evaluation job you requested has completed - possible new issues were detected. Report summary✖ Packages that failed9 packages failed only on the current version.
16 packages failed on the previous version too. ✔ Packages that passed tests3 packages passed tests only on the current version.
58 packages passed tests on the previous version too. ~ Packages that at least loaded3 packages successfully loaded only on the current version.
24 packages successfully loaded on the previous version too. |
|
that's better. so there are ~5 real failures, all of which are trying to drop non-trailing singleton dimensions besides FYI I tried to outline the error path, but it looks like there are bootstrap issues with |
|
triage also considered the fact that this implementation would allow |
|
Just to clarify: ignoring the axes offset in |
|
correct; this PR should not change the behavior of the MWE there although it may add documentation clarifying that this is allowed |
Just something to get the docs discussion started
|
I threw a commit on here that tries to document this; it's just meant to be a starting point. |
|
not to add another wrinkle but should this PR also remove the Line 1028 in 13f6b3b if we are going to really commit to "sizes must match, axes need not" decision |
|
I will need help coordinating with JuliaSparse/SparseArrays.jl#637 |
|
I'm going to run a bunch of benchmarks for |
notnow ambitious enough to claim this fixes #40018, but let's just say I wrote it while reading the issuefixes JuliaSparse/SparseArrays.jl#569
updates #45374 (closes?)