#17130: Coercion after _eval_() in symbolic functions
-----------------------------+------------------------
Reporter: jdemeyer | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-6.4
Component: symbolics | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
-----------------------------+------------------------
Comment (by kcrisman):
I'm not surprised - the problem is that this kind of code was added at
various times to handle certain cases where the output was not the same
type as the input (e.g., complex output for real/`float` input). For
instance, does the example mentioned in the code
{{{
arctan(RR(1))
}}}
work properly with this patch? Again, I'm sorry I don't have time to do
more than read code for five minutes at this point :(
Edit: I see your most recent comment - yes, that would certainly be
helpful, though I have a feeling a '''LOT''' of functions would have to be
fixed... because some probably implicitly rely on this block but aren't
thoroughly tested for unusual input/output.
--
Ticket URL: <http://trac.sagemath.org/ticket/17130#comment:7>
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.
