#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):
Just adding something : unless this ticket is reviewed I will have to
implement the caching method manually in 4 different functions.
I also forgot to add another reason for having a function like that :
A cached function cannot (safely) return mutable answers. If you return a
list and that the user modifies the list, then it also modifies the list
stored in the function's cache.
Thus, as my functions return some mutable answers (lists) which I do not
want to cache but I am forced to, I have to turn them into tuples before
returning them (which again triggers useless copies later). With the 10
lines from this branch I would be able to say that I don't want to cache
those answers. Which I never wanted to cache anyway.
Just saying...
Nathann
--
Ticket URL: <http://trac.sagemath.org/ticket/16353#comment:35>
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.
