-
-
Notifications
You must be signed in to change notification settings - Fork 528
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
Witt vectors redone #39355
base: develop
Are you sure you want to change the base?
Witt vectors redone #39355
Conversation
The skeleton of the planned structure of Witt Vectors is implemented. There is essentially no functionality yet.
Documentation preview for this PR (built with commit 3d34b15; changes) is ready! 🎉 |
The term "Witt ring" refers to various objects Use "Witt vector ring" instead to remove any confusion
In the litterature, p-typical Witt vectors refer to this construction as oppososed to big Witt vectors Remove the wrong mentions in the code to reflect that Greatly simplifying it in the same time
Remove the 'auto' and 'none' keyword and handle None instead Add more liberty and exceptions in the general constructor
I had no clue what "otf" meant so I changed to a clearer algorithm name
We add documentation for every method, and also provide tests Thanks to the tests we discovered bugs which have been fixed The fix led to the use of __classcall_private__ instead of the previous constructor
@fchapoton C'est bon pour moi, si les tests passent. |
To everyone: I did a major cleanup of @nielrenned's code on Witt vectors during SageDays 128. My hope is to see this code finally merged into SageMath. I wonder though whether the function |
This is based on the work from #11457, refreshed and cleaned up a little bit.
Still needs a lot of work on documentation and doctests : there are currently ZERO doctests.
📝 Checklist