-
Notifications
You must be signed in to change notification settings - Fork 67
Add ones for NCRing #1886
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
base: master
Are you sure you want to change the base?
Add ones for NCRing #1886
Conversation
Also simplify zeros implementation and add some tests
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1886 +/- ##
==========================================
- Coverage 88.13% 88.13% -0.01%
==========================================
Files 120 120
Lines 30286 30281 -5
==========================================
- Hits 26694 26689 -5
Misses 3592 3592 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fill
fills the array with aliases elements. We usually don't want this, but instead every zero or one entry should be it's own object
Hrm, I am torn on this. We "usually don't want that" for our own matrices, but it is what
Of course this is not practical for actual use within OSCAR, but that's not what this is about. Perhaps this is an argument to turn both of these functions into just error like |
I don't consider it a problem that all elements are identical. |
We just had someone on slack that was trapped by the julia behavior. |
We had a discussion related to this during yesterday's triage and basically I now think that while "formally and legally" my new methods are "correct", they are footguns waiting to be triggered, so I now tend to agree that if we add |
Also simplify zeros implementation and add some tests (see also oscar-system/Oscar.jl#2231)