Hi Dima, On 2019-07-12, Dima Pasechnik <dimp...@gmail.com> wrote: > Hi Simon, > isn't MeatAxe interfaced via a library, rather than via files?! > Doing arithmetics on small matrices storing them on a disk is insanely > inefficient...
Maybe. Do you mean one should instead compute a new multiplication table in memory in each individual Sage session, rather than reloading previously computed tables? Would that be more efficient? Reloading is the design choice of MeatAxe, which I preserved when I forked it to create SharedMeatAxe. Of course, it might be possible to diverge even further from upstream and change SharedMeatAxe (which is used in Sage) to not use these files. Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/qga2lu%24d4r%242%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
