Closed lukas-weber closed 7 months ago
The line causing the exception on the latest master 71f68b4c is as follows:
@lukas-weber Could you please post the full stacktraces and a copy-pastable code example for the complex Dual case. One possibility is to catch this case earlier at the lu
/factorization level, another one is to catch it at the generic triangular solve level. That would be easier to judge given the stacktraces.
Perhaps it's better to solve it in triangular solve as it will also be solved for the vanilla L \ b
when used independently of lu
? What I saw at that time was that in the other "graceful" cases, it works because the loop variables are not accessed outside of the loop over their size. But, in this case, amm
is accessed before the loop over m
, perhaps for efficiency reasons.
@lukas-weber Could you please post the full stacktraces and a copy-pastable code example for the complex Dual case. One possibility is to catch this case earlier at the
lu
/factorization level, another one is to catch it at the generic triangular solve level. That would be easier to judge given the stacktraces.
They are added now. Sorry for the inconvenience!
Many parts of julia linear algebra handle empty matrices gracefully, which is helpful when writing codes where they appear as a corner case. However, dividing LU-decompositions of generic numbers will yield a SingularException instead.
It is worth noting that doing the same with complex Dual numbers on 1.10.1 will lead to segfaults as well. In the nightly, I was not able to reproduce that so I assume it has been fixed.