-
-
Notifications
You must be signed in to change notification settings - Fork 565
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
Remove binary_function from ginac's code in sage #34573
Comments
comment:1
We should take a look at what upstream did with the affected code (see #33401). They had many C++ cleanups over the years. |
comment:2
That is true, but right now I will just focus on that bit. Most of the time just removing the offending characters works. In real time, it appears to have compiled cleanly locally. Moving on doctesting. |
comment:3
Upstream did this change in 319c9533e12eba2449001c47545e3c3cf48c482f |
comment:4
Right, I supposed I should discard what I have just done and use that instead. It should have gone through more testing. |
comment:5
I never thought about that before, how do I track a hash down on github? Do You have to check out and search with git manually? |
comment:6
Only tried this out now, but a global search for that sha finds repo & commit! |
comment:7
OK, that's interesting. So, my patch includes touching one file not in that commit because it is not in that repository. And the commit touches files we do not have in sage. Where they overlap, my job is identical to one white space difference. So, I think I'll just send my branch and we'll think about synchronisation later because that won't be fun. |
comment:8
Yes, I agree. |
Branch: u/fbissey/binary_function |
Commit: |
New commits:
|
Author: François Bissey |
Reviewer: Matthias Koeppe |
comment:11
positive review from gentoo user |
Changed branch from u/fbissey/binary_function to |
The use of
std::binary_function
andstd::unary_function
have been deprecated for almost 10 years and gcc-12 is now signalling it. They may be completely removed soon. We get the following warnings when building sageThe following files contain offending code
There are no instances of
unary_function
in sage.I did a similar clean up in brial quite recently https://github.com/BRiAl/BRiAl/pull/52/files
CC: @antonio-rojas
Component: porting
Author: François Bissey
Branch/Commit:
0dc211b
Reviewer: Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/34573
The text was updated successfully, but these errors were encountered: