#17412: improve documentation of 'solve()'
-------------------------------------+-------------------------------------
Reporter: jakobkroeker | Owner:
Type: enhancement | Status: needs_info
Priority: minor | Milestone: sage-6.5
Component: documentation | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/jakobkroeker/ticket/17412 | 2d7574794ae840b48a0f8841a8978157066982db
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Changes (by jakobkroeker):
* status: new => needs_info
* commit: => 2d7574794ae840b48a0f8841a8978157066982db
Comment:
What is about
{{{
solve_mod()
solve_ineq_univar()
solve_ineq_fourier()
solve_ineq()
}}}
may they also fail in some cases to return all solutions?
Which other routines need an explicit statement, that an empty result does
not imply
that there are no solutions?
----
New commits:
||[http://git.sagemath.org/sage.git/commit/?id=2d7574794ae840b48a0f8841a8978157066982db
2d75747]||{{{explicitly state that solve may not obtain all existing
solutions and that an empty result does not imply there are no
solutions}}}||
--
Ticket URL: <http://trac.sagemath.org/ticket/17412#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.
For more options, visit https://groups.google.com/d/optout.
