I have figured out what was going wrong: after #17272, the *generic* algorithm was being called rather than the specific implementation, which was still called _echelon_in_place_classical. I have added a _echelon_in_place to the meataxe matrices to simply call this. We probably should have design discussion about how to best work the code for potentially different algorithms for different matrix implementations. At least, it seems to be the current framework is not so sustainable as-is.
Best, Travis On Thursday, May 31, 2018 at 7:28:44 PM UTC+10, Simon King wrote: > > Hi Vincent, > > On 2018-05-31, Vincent Delecroix <20100.d...@gmail.com <javascript:>> > wrote: > > I have no idea which ticket introduced this change but it used to work > > fine on beta2. > > Travis said it might be #17272. Anyway, I am at it, and hope to fix the > problem in the next few days. > > Best regards, > Simon > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
