Comment #4 on issue 3585 by [email protected]: Replace new assumptions handlers
http://code.google.com/p/sympy/issues/detail?id=3585
Ah, I see, we have to consider relationships between n classes and m predicates. Both solutions require that when you add one on one side you need to navigate through all of the others.
It looks like new assumptions chooses to organize information first indexing by predicate, then by class. Old assumptions chooses to organize information first by class then by predicate. Is there a solution that breaks out of this ambiguous choice? Is there a better organization pattern that does not have to make this choice yet is still efficient to query?
It looks like each side has some useful hierarchical structure. Classes have a class hierarchy (e.g. S.One is an Integer) and predicates have implications (e.g. positive numbers are real). Are we taking full advantage of this structure?
-- You received this message because you are subscribed to the Google Groups "sympy-issues" 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-issues?hl=en.
