#13378: Do not cache the non-existence of coerce/convert map too often, and do
not
pretend that there is a conversion where it doesn't make sense at all
----------------------------------------------------+-----------------------
Reporter: SimonKing | Owner: robertwb
Type: defect | Status: new
Priority: major | Milestone: sage-5.3
Component: coercion | Resolution:
Keywords: coercion conversion object cache | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
----------------------------------------------------+-----------------------
Comment (by SimonKing):
Replying to [comment:2 nbruin]:
> I know this all flies in the face of duck typing, but so does the whole
category framework.
One could say that the category framework is the opposite of duck typing:
In duck typing, you'd test whether certain methods are available for X,
and conclude that X belongs to the category of ducks. In the category
framework, you would at some point initialise X as an object of the
category of ducks, and the category then provides X with methods like
"quack()", "swim()", "fly()" --- or, if the category framework can not
provide generic methods, it does require that these methods are
implemented.
But I actually think that's a strength of the category framework. And note
that after category initialisation of X, it would to some extent be
possible to determine `X.category()` from the methods X provides.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13378#comment:4>
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.
