> How do you know what the user considers "small" and "large"?
In my case it is straightforward, but I could want to use this feature is my own personal code anyway. > And if you really need to decide whether to cache or not based on the > arguments, you have to manage your own cache. Well, I had to work on graphs with my own code before it was merged into Sage, too. > Using some condititonal that you can pass to the memoization decorator is a > spectacularly ugly way of managing your own cache. For starters, it doesn't > allow you to make the caching decision on intermediate values of your > computation. I don't know how to implement that with the caching mechanism. Okay guys, it is 100 against one as always, you keep ignoring the fact that the feature may be useful despite two messages coming from other persons, you ignored my questions about the current "key" argument, so I have no choice but to re-implement the feature in my own code, and those who also need it will do the same. I would have liked to see you all so fierce when I complained about the combinatorial_map decorator. Too bad ! Nathann -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
