#20920: Changes to Unknown class
-------------------------------------+-------------------------------------
Reporter: eviatarbach | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: sage-7.3
Component: misc | Resolution:
Keywords: days78 | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/eviatarbach/unknown | 7d95643efc6699998240ba08c95006ae4fd9c482
Dependencies: #20919 | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by vdelecroix):
What is the point of an `Undecidable` class? To my mind this is completely
useless.
- either you have an algorithm that works sometimes (because the problem
is undecidable). If an instance of this algorithm fails, then you should
raise an error or possibly returns `Unknown`.
- or you have no algorithm for a given problem and it makes no sense to
write an empty Python function for that.
--
Ticket URL: <https://trac.sagemath.org/ticket/20920#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 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.
