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
Support C++17 code in packages #25255
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:3
What is this ticket about? The description reads more like a comment than an actual issue to be solved. If the ticket cannot be made more concrete, I suggest closing it. We can always open a ticket whenever a real problem occurs. |
comment:4
I have an implementation of commutative matching (needed to fix #25168) in the works that depends on |
comment:5
Note also that #25168 is more an enhancement as the old behaviour will stay for backward compatibility (in principle it's good to have many different types of matching algorithms). |
comment:6
Actually, even Python2.7 (not 3.4) has |
comment:7
A Trac ticket is about a concrete issue to be fixed. The stuff you are talking about fits more on a mailing list, wiki or something like that. |
comment:8
I agree. I just replaced |
comment:10
closing positively reviewed duplicates |
This is at the moment a ticket for a nonexisting defect, as no standard package uses C++17 code at the moment.
The compiler situation is that C++17 is fully supported by
clang++-4 --std=c++17
andg++-7 --std=c++17
. So, compiler-wise Sage could support it without raising requirements (currently at g++-4.8) by building g++ if system has g++<7. But for full supportlibstdc++-gcc7
orlibc++-4
is needed too, sog++-7
would be the system requirement.How much is gcc-7 already in the wild?
Another issue is that with g++-5 I think and clang++-4 the
register
keyword became deprecated and will be removed with C++17 where it will cause a compiler error. This affects at least Singular and Giac.Component: build
Issue created by migration from https://trac.sagemath.org/ticket/25255
The text was updated successfully, but these errors were encountered: