Skip to content
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

fix m prototype #175

Merged
merged 1 commit into from
Jan 10, 2025
Merged

fix m prototype #175

merged 1 commit into from
Jan 10, 2025

Conversation

dimpase
Copy link
Member

@dimpase dimpase commented Jan 7, 2025

instead of #134, just use the important commit. This will fix #133

@dimpase dimpase requested a review from tornaria January 7, 2025 20:34
@dimpase dimpase mentioned this pull request Jan 7, 2025
@AurelPage
Copy link

AurelPage commented Jan 10, 2025

Hi, I don't know how cypari is implemented, but this looks reasonable to me. Note that in gp, if the result of the function with prototype m is not returned to the user (for instance it is immediately used in another function call) then we don't do the gcopy. I don't know whether this is possible in cypari. I will also show the patch to Bill.

@AurelPage
Copy link

Bill says that if new_gen makes a copy then gcopy is unnecessary. But seeing #133 it seems that this is not the case.

@dimpase
Copy link
Member Author

dimpase commented Jan 10, 2025

Bill says that if new_gen makes a copy then gcopy is unnecessary. But seeing #133 it seems that this is not the case.

Indeed, I can confirm that not doing copy in the patch does not fix #133, while this one does.

@dimpase dimpase merged commit 37acf81 into sagemath:master Jan 10, 2025
84 of 115 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

member functions and memory
3 participants