New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EmptySet is Back ! TestSuite should allows for empty sets. #8543
Comments
Attachment: trac_8543-empty_set_categories-fh.patch.gz |
Changed keywords from empty set, Testsuite to empty set, Testsuite, EmptySetError |
This comment has been minimized.
This comment has been minimized.
comment:2
Patches from #8519 your patch apply fine on 4.3.4 Thanks for fixing this! I give this patch a positive review... |
Reviewer: Nicolas Borie |
comment:3
Nicolas: thanks for your review! Florent: I made a quick reviewer patch fixing some trivial things. Please double check, and set back the positive review! |
comment:4
Attachment: trac_8543-empty_set_categories-review-nt.patch.gz |
Changed reviewer from Nicolas Borie to Nicolas Borie, Nicolas M. Thiéry |
comment:7
The new changes are good to me => positive review. |
Merged: sage-4.4.alpha0 |
comment:8
Merged in 4.4.alpha0:
|
There is currently no way to have an empty set which pass the category tests. Indeed the current specification says: for any set
S
there must be a methodS.an_element()
which returns an actual elementx
such thatx in S
:This tests should allows
S
to be empty.To solve this issue I added a new exception called
EmptySetError
which should be raised in such cases. I fixed the tests suite of the categorySets()
accordingly and expanded the test in some places where this could be done before.Depends on #8519
CC: @sagetrac-nborie @sagetrac-sage-combinat
Component: categories
Keywords: empty set, Testsuite, EmptySetError
Author: Florent Hivert
Reviewer: Nicolas Borie, Nicolas M. Thiéry
Merged: sage-4.4.alpha0
Issue created by migration from https://trac.sagemath.org/ticket/8543
The text was updated successfully, but these errors were encountered: