Am 07.11.2013 05:42, schrieb Aaron Meurer:
Yes, we still need multiple dispatch,
I'm wondering - what do we need that for? What problem does it solve?
> but it's a really hard problem,
Actually, a wrapper-based solution shouldn't be too hard to do, so the
implementation side of things is just the amount of work.
At the conceptual level, it's indeed hard, it involves trade-offs with
nonobvious consequences.
I once tried to work it out for Eiffel, or for statically-typed
languages, and found (to my dismay) that it involves trading off
language properties that I all considered essential. (I do not think
that having a dynamically-typed language like Python helps here; in my
experience, dynamic typing just shifts the problem from the language
designer's shoulders to the library designer's shoulders, with the
library designers having less experience to deal successfully with the
issues.)
However, with a concrete goal in mind and when applying it to a
restricted problem domain, maybe a trade-off can be found that might work.
That's why I'm asking about the problem. Knowing the problem would help
me finding the path of least pain.
> no one has been working on it
Yeah, and I'm not volunteering either since my time is too limited.
What I can do is describe the issues and enable informed design decisions.
> I'm not even sure what the best solution is yet
What trade-offs are on your radar there?
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sympy.
For more options, visit https://groups.google.com/groups/opt_out.
