#5598: [with patch, needs work] allow post-creation (pre-use) declaration of
coercions
----------------------+-----------------------------------------------------
Reporter: robertwb | Owner: robertwb
Type: defect | Status: new
Priority: major | Milestone: sage-3.4.2
Component: coercion | Keywords:
----------------------+-----------------------------------------------------
Comment(by nthiery):
I have been using this patch (or actually a plain python version of it;
see the sage-combinat patch queue) relatively intensively, and it does its
job well. However it's hard to extract any interesting unitary test from
those uses, since they all rely on the rest of the category stuff.
I have just attached a stupid test instead ... It just plays with
register_coercion, but should be easy to adapt to the others.
Btw: robert: would it be possible to have register_coercion just raise a
warning if coercions have readily been used? There are cases where it can
be handy to abuse the system a bit from the interpreter.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/5598#comment:7>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
