On Fri, 1 Feb 2013, Dima Pasechnik wrote:
If I understand correctly, after conjugacy_class(self, g) is done it needs
only say conjugacy_class(self, g1)==conjugacy_class(self, g2) to check if
This is not efficient - -
True.
Should Sage aim to efficient code whenever something is added, or should
we just put in something that works and lock "user interface", i.e.
command or function name, order of arguments etc?
I guess this depends what you think our target audience is. Somebody
taking first class of algebra wants code that works and is easy to use,
and is going to use groups of small size anyway. Some other user will not
like code that works in principle but is too slow to use in real cases.
--
Jori Mäntysalo
--
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 http://groups.google.com/group/sage-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
