Skip to content

docs: update supported compiler versions to match the C++17 requirement - #1404

Open
DiamonDinoia wants to merge 1 commit into
xtensor-stack:masterfrom
DiamonDinoia:docs/compiler-versions
Open

docs: update supported compiler versions to match the C++17 requirement#1404
DiamonDinoia wants to merge 1 commit into
xtensor-stack:masterfrom
DiamonDinoia:docs/compiler-versions

Conversation

@DiamonDinoia

Copy link
Copy Markdown
Contributor

The listed versions (MSVC 2015 update 2, g++ 4.9, clang 4.0/3.7) predate C++17 and cannot compile the library. Minimum versions with full C++17 language support per the official compiler documentation.

The listed versions (MSVC 2015 update 2, g++ 4.9, clang 4.0/3.7) predate
C++17 and cannot compile the library. Minimum versions with full C++17
language support per the official compiler documentation:

- GCC 7 (gcc.gnu.org/projects/cxx-status.html)
- Clang 5 (clang.llvm.org/cxx_status.html)
- VS 2017 version 15.7 (Microsoft C++ conformance table; VS2017 releases
  are named 'version 15.x', not 'update N')

Assisted-by: Claude <noreply@anthropic.com>
@Alex-PLACET

Copy link
Copy Markdown

I propose to reference those we have in the CI:
gcc 10
clang 16
MSVC 2022
If we plan to support older compilers, we should add them in the CI

@DiamonDinoia

Copy link
Copy Markdown
Contributor Author

I have no problem with that. I personally dislike maintaining very old compilers but I leave htis decisions to you all.

@JohanMabille

Copy link
Copy Markdown
Member

It's indeed complicated to maintain compilers that we don't test in the CI, so I agree with Alexis, let's require those from the CI as minimal versions

@DiamonDinoia

DiamonDinoia commented Aug 28, 2026 via email

Copy link
Copy Markdown
Contributor Author

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.

3 participants