Comment #5 on issue 1908 by [email protected]: mutable core http://code.google.com/p/sympy/issues/detail?id=1908
Of course, an efficient implementation has to use mutable structures internally. But this is quite unrelated to the mutability of the object itself. To get an "immutable" object, you only need a __hash__() and to ensure that the equality relation is constant wrt. time (i.e. if a == b at one time, then it is true at all times).
IIRC, the sympycore solution is to consider objects initially mutable until their
hash is computed, and immutable afterwards. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- 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.
