>
>
> 1) On multidispatch itself: You can have either modularity or freeness
> from surprises (this has been discussed before - essentially, if you have
> modularity, adding a module with new MD definitions can change dispatch
> decisions for related combinations of types).
> This isn't a problem inside SymPy where we do not expect average users to
> develop subclasses of existing, multi-dispatching SymPy object classes. It
> might become a problem if multi-dispatch is made an independent module.
>
Multipledispatch supports namespaces. If someone wants to extend the sympy
namespace they need to do
from sympy.dispatch import dispatch
@dispatch(MyClass)
def foo(x):
...
So in general conflicts can happen but they're unlikely to happen by
accident.
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sympy+unsubscr...@googlegroups.com.
To post to this group, send email to sympy@googlegroups.com.
Visit this group at http://groups.google.com/group/sympy.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sympy/CAJ8oX-EqZKpCPdVS9HoFy9iao7n%3DBUM0YZ40DeEH-%3DdU8j_mZA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
