-
-
Notifications
You must be signed in to change notification settings - Fork 488
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
Bug in initialisation of species #12649
Comments
comment:1
Here is a smaller code which triggers the problem:
|
comment:3
Fixed in #15673. |
comment:7
will this be fixed by the recent refactoring ? maybe check also other tickets with "species" keyword ? |
comment:8
Yes, this already works. However, you have to be explicit about the valuation of (I admit I don't see right now whether it should be able to determine that the valuation is not 0 - do you?)
|
comment:9
Yes, I am eager to close all the other tickets. However, I want #34552 to be in the develop branch first. |
comment:10
Hm, I think it should know that the valuation is greater than 0. The valuation of
I'm not sure yet. |
Changed keywords from Species to Species, LazyPowerSeries |
comment:12
We actually thought about this situation (I forgot), and introduced a I am still not sure what the best solution might be. |
Fixed by #36284. |
The following specification is valid:
However, the following code breaks
Strangely enough, adding some seemingly unrelated instruction work
around it::
Florent
CC: @sagetrac-sage-combinat @mantepse
Component: combinatorics
Keywords: Species, LazyPowerSeries
Issue created by migration from https://trac.sagemath.org/ticket/12649
The text was updated successfully, but these errors were encountered: