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
cluster seed is no longer hashable #19440
Comments
Changed keywords from none to cluster |
comment:2
here is a branch not working yet New commits:
|
Branch: public/19440 |
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:5
Your changes look fine to me. In general, I am worried that the code gets slower and slower... I would like to do a few tests whether this also applies to your proposed changes. |
comment:6
stupid question (here and elsewhere): how do I see which version your code is based on? I would prefer not to pull it and check it out to then see that I first have to recompile sage for many hours. |
comment:7
Okay, got it: |
comment:8
Okay, it was slow and it is not slower now... |
Reviewer: Christian Stump |
Author: Frédéric Chapoton |
comment:10
Fails on 32-bit
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed branch from public/19440 to |
With the recent change in the cluster code,
And this has very bad consequences !
CC: @tscrim @darijgr @egunawan @sagetrac-gmoose05 @stumpc5
Component: combinatorics
Keywords: cluster
Author: Frédéric Chapoton
Branch/Commit:
be4fa45
Reviewer: Christian Stump
Issue created by migration from https://trac.sagemath.org/ticket/19440
The text was updated successfully, but these errors were encountered: