#16353: A cached_function with selective memory
-------------------------+-------------------------------------------------
Reporter: | Owner:
ncohen | Status: needs_review
Type: | Milestone: sage-6.3
enhancement | Resolution:
Priority: major | Merged in:
Component: | Reviewers:
performance | Work issues:
Keywords: | Commit:
Authors: | 7eb8f900f1a143c6cc85b9382a365b57a9c42ecc
Nathann Cohen | Stopgaps:
Report Upstream: N/A |
Branch: |
u/ncohen/16353 |
Dependencies: |
-------------------------+-------------------------------------------------
Comment (by ncohen):
> I told you already on sage-devel that you don't need this, the sooner
you refactor your code to use sane function names the quicker we can close
this ticket as invalid.
This ticket is not invalid, this ticket implements a feature I need, and a
feature that several other developpers acknowledged as being potentially
useful. I don't even get how you can honestly deny that filtering what is
being cached, even if the two functions "don't talk", can be useful.
Stop this game and look at the code. It does not slow anything down
because it is a new class, it solves my problem and it is clearly the kind
of stuff that other persons may need too. There's no reason to refuse it a
priori.
Nathann
--
Ticket URL: <http://trac.sagemath.org/ticket/16353#comment:21>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" 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/sage-trac.
For more options, visit https://groups.google.com/d/optout.
