#15200: _evalf_ handling of backends
-------------------------------+-------------------------
Reporter: eviatarbach | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: sage-5.12
Component: symbolics | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: #12289 | Stopgaps:
-------------------------------+-------------------------
Comment (by eviatarbach):
I think "the right thing if it is not given" is resort to a method
`_evalf_default_`. In cases where `_evalf_` has already been defined,
overwriting the `_evalf_` which this patch would define, this will not
change anything. The only problem is that for most functions the
`algorithm` keyword won't do anything. I can't think of any good solution
to this (such as raising a warning or error) that wouldn't involve
modifying all the existing symbolic functions.
--
Ticket URL: <http://trac.sagemath.org/ticket/15200#comment:2>
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/groups/opt_out.
