On Friday, June 3, 2016 at 12:42:29 PM UTC-7, Volker Braun wrote: > > > I understood what you want, but I'm saying that its bad to have a bug in > the code that is then worked around by a decorator. Just don't put the bug > in the code to begin with. Apart from being the right thing to do, its also > much more maintainable. >
It could be that the undecorated code is bug-free,e.g. def list_of_copies_of_mutable_constituents(self): return [copy(a) for a in self.mutable_stuff] With this code it's safe to so L = A.list_of_copies_of_mutable_constituents() L[0].mutate() A change in behaviour now gets introduced by slapping on a @cached_method, and this doesn't even get fixed by using a tuple instead of a list. There is room for cached_method to help with this. I just don't see how it can automatically guess the right thing to do. -- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
