#8821: Adding a section on coercion to the tutorial (guided tour)
-----------------------------+----------------------------------------------
Reporter: SimonKing | Owner: mvngu
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-4.4.1
Component: documentation | Keywords: tutorial coercion
Author: Simon King | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------------+----------------------------------------------
Comment(by leif):
Replying to [comment:3 SimonKing]:
> > Second, we don't want to create the expectation that Python elements
are unique, as they usually aren't:
>
> Right, that should be clarified.
Yes, that's what I suggested in the {{{sage-devel}}} thread. ;-)
(And Robert noted that this is implementation-specific even in plain
Python.)
One should clarify that in general
{{{a is b}}} => {{{a == b}}}
but not necessarily the opposite.
Regarding comparison:
It should be stressed that not only {{{a == b}}} returns {{{False}}} if
coercion fails but also {{{a != b}}} (silently) returns {{{False}}} in
that case.
Reading on...
Btw (ticket description), I'd still say Sage's coercion ''is'' (a kind of)
implicit type conversion...
It seems we've reached ultimate confusion in the {{{sage-devel}}} thread
("exact" and "inexact" domains); I unfortunately haven't been able to
reply so far...
-Leif
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8821#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.
