You're right in that they both redundantly serve as immutable storage classes. I can envision a system where they're merged.
On the other hand one can think about them quite differently. Tuples contain Basics, IMs contain Exprs (not sure this is actually enforced.) Most importantly IMs have all the matrix computation stuff attached to them, Tuples are simpler. Were you thinking of subclassing IM from Tuple, subclassing Tuple from IM? Creating NDArray? What is the situation? Why does Tuple/IM require a special case? There has also been talk of removing Tuple entirely. You could pursue that as a solution. On Fri, May 11, 2012 at 7:12 PM, Chris Smith <[email protected]> wrote: > On Sat, May 12, 2012 at 5:36 AM, [email protected] > <[email protected]> wrote: > > Can we merge them? It will be useful for my gsoc project (I wont have > > to make special cases for Tuple). > > What do you have in mind for the merge? (IM has 2 shape parameters and > Tuple does not.) > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/sympy?hl=en. > > -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
