Skip to content

Conversation

@sbstndb
Copy link
Contributor

@sbstndb sbstndb commented Apr 4, 2025

Checklist

  • The title and commit message(s) are descriptive.
  • Small commits made to fix your PR have been squashed to avoid history pollution.
  • Tests have been added for new features or bug fixes.
  • API of new functions and classes are documented.

Description

Previously, xtensor uses c++17 as default.
Here is a PR that set c++20 by default.
This PR also suggests modifying the compilation option CPP20 to CPP23.

sbstndb and others added 9 commits April 3, 2025 10:45
	-	Previously, we had the option of activating c++20.
	-	But as we defined c++20 as default, I suggest to replace
			this option as c++23.
	-	Previously, tests was in c++17
	-	We want to add c++20 by default, so I modify the test cmake
	-	The tests passed locally
	-	Previously, The MSVC version was not well recognized
		--> Hence, there was some bugy macro specific to MSVC/c++20
	-	This Commit resolve the issue and I am now able to
			compile the problematic testcase
	-	Question : SHould we add this flag not at the tets level
			but at the main CMakeFiles level ?
	-	Previously, on MSVC, in c++20, the empty() function was incorrectly deduced
	-	Hence the test_xbuilder no longer pass
	-	I suggest enforce the right specialization by specifying the last template parameter
@JohanMabille JohanMabille changed the title feat: [WIP] Use cpp20 by default feat: Use cpp20 by default Apr 9, 2025
@JohanMabille JohanMabille merged commit 7910a2d into xtensor-stack:master Apr 9, 2025
16 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.

2 participants