#14592: Use lazy strings for error messages in coercion
-----------------------------------------------+----------------------------
Reporter: SimonKing | Owner: tbd
Type: enhancement | Status: new
Priority: major | Milestone: sage-5.10
Component: performance | Resolution:
Keywords: lazy error message coercion | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: #14585 | Stopgaps:
-----------------------------------------------+----------------------------
Comment (by SimonKing):
I see no gain in the (not posted) patches I tried. Even though certain
type errors are raised a couple of hundred times, it is still not
noticeable if we save "a couple of hundred times 1ms" in a computation
that takes a couple of seconds.
Do you have a striking example, in which computing a string representation
for creating an error message really hurts?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14592#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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
