-
Notifications
You must be signed in to change notification settings - Fork 66
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
Add Base.vec(M::MatElem)
#1614
Add Base.vec(M::MatElem)
#1614
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #1614 +/- ##
==========================================
- Coverage 86.98% 86.96% -0.03%
==========================================
Files 114 114
Lines 29686 29695 +9
==========================================
Hits 25823 25823
- Misses 3863 3872 +9 ☔ 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.
Not clear to me if we want this.
If we don't want this, this shouldn't be in Oscar as well (pinging @fieker). But I think we should definitely have a cheap way to convert a matrix to a vector (or 1xn / nx1 matrix) |
On Mon, Feb 19, 2024 at 04:32:07AM -0800, Lars Göttgens wrote:
> Not clear to me if we want this.
If we don't want this, this shouldn't be in Oscar as well (pinging @fieker).
It is/ was neccessary, if we want this, it also needs to be done in Nemo
for the Nemo types.
…
But I think we should definitely have a cheap way to convert a matrix to a vector
--
Reply to this email directly or view it on GitHub:
#1614 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
|
Co-authored-by: Max Horn <[email protected]>
|
I am happy to rename it to |
This seems to be controversial and I also don't see a good way to implement this efficiently without a lot of effort. So is this really worth pursuing? If @lgoettgens still has need, perhaps we should discuss it during triage? |
Iirc we resolved the problem in a different way |
The code originates in https://github.com/oscar-system/Oscar.jl/blob/597398c594796cd2abbd8749977cb3f2a20eefb2/experimental/GModule/GModule.jl#L1451, but I want to use it in other parts of Oscar, that should not depend on experimental. So the cleanest solution is to add it here.
Note that this code currently operates in column-wise fashion (should this be changed?)
To reduce any conflicts in Oscar, it would be easiest to include this in the next breaking release, and then remove the corresponding things in https://github.com/oscar-system/Oscar.jl/blob/597398c594796cd2abbd8749977cb3f2a20eefb2/experimental/GModule/GModule.jl#L1451.