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
Stopgap for IntegerListsLex #17637
Comments
Branch: public/17637 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Commit: |
comment:3
Since #17548 is about |
comment:4
In the code, it is said that the constraints are "assumed to be correct". I have no idea what happens if Nathann |
comment:6
Thanks Nathann |
comment:7
Reviewer name missing |
Reviewer: Jeroen Demeyer |
Changed branch from public/17637 to |
comment:10
As far as I can see from #17548 there are actually no known bugs with regards to IntegerListsLex. So I find it a total overreaction to put a stopgap as the limitations of IntegerListsLex are correctly documented. Now warnings appear in many parts of the code which are completely unrelated to this issue (and as I said, there does not appear to be a bug). For example
or
both of which are totally fine! Best, Anne |
Changed commit from |
comment:11
Dear Anne,
What about those examples from #17548 ?
I will answer other points on #17898. Nathann |
comment:12
Replying to @nathanncohen:
Read the answers that Travis gave on that ticket. They are consistent with the specifications or bad user input. Anne |
As reported on #17548, the class
IntegerListsLex
returns wrong result. Until this is fixed, we need a stopgap to warn users.Component: combinatorics
Author: Nathann Cohen
Branch:
5f00624
Reviewer: Jeroen Demeyer
Issue created by migration from https://trac.sagemath.org/ticket/17637
The text was updated successfully, but these errors were encountered: