> > > The reason to wonder is that it seems to provide methods to a polyhedron > > object which make no sense: > > > > > > .is_idempotent() > > .is_zero() > > .n() > > .numerical_approx() > > .subs() > > .substitute() > > This is a *mess* that should actually be removed from Element! > > Okay, that explains somehow the origin of that. So, among all the classes that inherit from Element, such scenario repeats itself I guess?
Hmm... Hopefully none require such methods... Should this be a ticket then? > Element is good when you want coercion to be involved. Such coercion > might be useful for polyhdera when considering for example > > scalar x polyhedron > scalar + polyhedron > matrix x polyhedron > (polyhedron over R1) + (polyhedron over R2) > > True. That's good to have! Thanks for enlightening me! JP -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
