#9704: refactor "trace" -- make trace command call trace method on input if
available
---------------------------+------------------------------------------------
Reporter: was | Owner: jason
Type: enhancement | Status: needs_review
Priority: minor | Milestone: sage-4.5.2
Component: misc | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
---------------------------+------------------------------------------------
Comment(by jason):
Replying to [comment:4 was]:
> * jason -- trace already means two different things, at least. I'm not
adding a new meaning.
When I read the code, trace() has one purpose, not two. Your patch will
mean that the trace function has two completely different purposes,
depending on the input. That is what I'm -1 on.
If we change the trace() function so that it instead computes the trace of
an object (i.e., x.trace()), then I agree that for a short amount of time,
a deprecation warning should be added and trace() will have to serve two
purposes.
>
> * regarding adding a deprecation warning, I think that is reasonable,
but that should not go in this ticket. If you want to do that, make it
another ticket and do it.
I'm -1 on a ticket (this one) which makes the Sage trace() function have
two purposes (unless it's a temporary thing that is deprecated, of
course).
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9704#comment:5>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
