#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: |
-------------------------+-------------------------------------------------
Changes (by kcrisman):
* status: positive_review => needs_review
* milestone: sage-duplicate/invalid/wontfix => sage-6.3
Comment:
> Okay guys, you won again ! I will just write three times the same
caching mechanism in three different functions, as it is clearly a better
design.
? I'm just going to point out that I didn't say anything about caching
design (just asked naive questions). Just about finding some compromise.
I'm sure something useful and agreeable will come out of this, even if
it's from someone else taking up the code later.
--
Ticket URL: <http://trac.sagemath.org/ticket/16353#comment:34>
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.
