#269: Add __mod__ to coercion model
----------------------------------+------------------------
Reporter: dmharvey | Owner: somebody
Type: enhancement | Status: new
Priority: major | Milestone: sage-7.1
Component: coercion | Resolution:
Keywords: | Merged in:
Authors: Jeroen Demeyer | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: #2034 | Stopgaps:
----------------------------------+------------------------
Comment (by jdemeyer):
Replying to [comment:19 vdelecroix]:
> In a situtation like `e1._mod_(e2)._add_(e3)` Cython would be happier.
No?
Sure, but I don't know how common that is.
I want to avoid unneeded checking. If you do something like
{{{
cpdef Element _foo_(self, other):
x = ...
return x
}}}
then Cython will add a check that `x` is actually of type `Element`. I
think (but this is just a wild guess) that the slow-down of these extra
checks does not justify the few cases where the check might improve
performance.
--
Ticket URL: <http://trac.sagemath.org/ticket/269#comment:20>
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 https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
