#17814: Make calling a cached method independent of source code inspection
--------------------------------+------------------------
Reporter: SimonKing | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-6.6
Component: distribution | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
--------------------------------+------------------------
Comment (by SimonKing):
Replying to [comment:12 jdemeyer]:
> Replying to [comment:7 SimonKing]:
> > Yes, we do require that.
> Is that really so important? Does it happen a lot in practice that
people or the Sage library call a function in different but equivalent
ways?
I believe it is important, and I think it is specified somewhere in the
docs of sage.misc.cachefunc. There are places where it is used for
`UniqueRepresentation`. Indeed, if you have a unique parent that depends
on arguments which (partially) have a default, then you simply don't know
if the user will provide these arguments explicitly or implicitly. But
when pickling/unpickling it, the arguments will be provided in a uniform
way (always explicitly, if I recall correctly).
Hence, if we changed that, we would break uniqueness of
`UniqueRepresentation` under pickling.
--
Ticket URL: <http://trac.sagemath.org/ticket/17814#comment:13>
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.
