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
Implement and use get_unsafe()/set_unsafe() for vectors #17562
Comments
Branch: u/jdemeyer/ticket/17562 |
Commit: |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Dependencies: #10513 |
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. This was a forced push. Last 10 new commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Author: Jeroen Demeyer |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Reviewer: Vincent Delecroix |
comment:21
Looks good. (follow-up: #18029) |
Changed branch from u/jdemeyer/ticket/17562 to |
Use
get_unsafe()
andset_unsafe()
in the generic__getitem__
and__setitem__
methods for free module elements (a.k.a. vectors).This should also fix
Depends on #17585
Depends on #17850
Component: linear algebra
Author: Jeroen Demeyer
Branch/Commit:
d250a42
Reviewer: Vincent Delecroix
Issue created by migration from https://trac.sagemath.org/ticket/17562
The text was updated successfully, but these errors were encountered: