-
-
Notifications
You must be signed in to change notification settings - Fork 565
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
Remove redundant classcall_private from partitions #14225
Comments
comment:2
Oops, I forgot to document the new cached function. Patch updated. |
This comment has been minimized.
This comment has been minimized.
comment:3
I think it is better to keep separate topics on separate tickets. Hence, I only remove |
Reviewer: Travis Scrimshaw |
comment:4
Could you rebase this over #11410 (which is essentially done)? Other than that, it looks good. Thanks Simon, Travis |
comment:5
I am just thinking: Shouldn't |
Attachment: trac_14225-partition_classcall_private.patch.gz |
comment:6
Done. |
comment:7
Looks good to me. Thank you, Travis |
comment:9
"Pending" because of #11410? |
comment:10
Yes, but in any case it would be sage-5.9, not sage-5.8. |
comment:11
Changing my mind because of #14228. |
Merged: sage-5.8.beta4 |
This is a follow-up to #13605. I think that several
__classcall_private__
methods in sage.combinat.partition are not needed.There are some
__classcall_private__
methods that do an extensive preprocessing, or that deal with optional arguments. I work on making the latter automatic. But currently, thee__classcall_private__
applications make sense.However, I doubt that a
__classcall_private__
method makes sense that simply puts aInteger(k)
around an argumentk
that is supposed to be an integer (python int or whatever). Since caching is by equality and since k as int, Integer, NN, QQ etc. evaluates equal, caching is not an issue here.Depends on #13605
Depends on #11410
CC: @sagetrac-sage-combinat @tscrim
Component: combinatorics
Keywords: partition classcall
Author: Simon King
Reviewer: Travis Scrimshaw
Merged: sage-5.8.beta4
Issue created by migration from https://trac.sagemath.org/ticket/14225
The text was updated successfully, but these errors were encountered: