-
-
Notifications
You must be signed in to change notification settings - Fork 480
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
Improvements to submodules #19448
Comments
comment:1
One thing that might be slightly controversial is that I construct an explicit ordering of elements used after the echelonization. However, this is needed to be stored in the submodule because if the ordering of the ambient changes (which it can by the New commits:
|
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:4
merge conflict |
comment:6
Actually, the more I think about it, the more I am for fixing the ordering of the submodule basis as the submodule is defined by a matrix, where there is an implicit ordering of the basis already in there. |
comment:7
failing doctest |
comment:9
This should now pass all tests. I also extended the |
Changed keywords from none to sd109 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:12
So doctests were failing elsewhere because |
comment:13
looks reasonable to me. |
Reviewer: Simon Brandhorst |
Changed branch from public/categories/improve_submodules-19448 to |
comment:15
Follow-up discussion in https://groups.google.com/g/sage-devel/c/z1k8IT3ocR4/m/UfkhlDweBwAJ |
Changed commit from |
We implement the lift map as a coercion map from a submodule and extend the submodule to work over modules with infinite bases.
CC: @jhpalmieri @nthiery @darijgr @avirmaux @fchapoton @mkoeppe
Component: categories
Keywords: sd109
Author: Travis Scrimshaw
Branch:
d8a1c50
Reviewer: Simon Brandhorst
Issue created by migration from https://trac.sagemath.org/ticket/19448
The text was updated successfully, but these errors were encountered: