Require C++20 and update to C++20 (#698)

* Require C++20 in podio and ROOT

* Use consteval when possible and remove checks for C++20

* Use concepts and simplify templates

* Change enable_ifs by requires

* Fix the documentation for links

* Remove an unused header and use std::disjunction

* Use algorithms from std::ranges

* Use concepts when possible and add comments when it's not possible

* Remove dead code

* Use std::ranges::find

* Remove the ubuntu workflow since it is built with C++17

* Update docs for the frame

* Add missing is_detected_v

* Upper-case the concept collectionType

* Add a minimum ROOT version with support for C++20

* Add back an ubuntu workflow with C++20

* Update the ROOT version

* Update README.md

Co-authored-by: Thomas Madlener <[email protected]>

* Change the format to C++20

* Make sure to also format links.md

* Remove no longer applicable enable_if from doc

* [format] clang-format auto fixes

---------

Co-authored-by: jmcarcell <[email protected]>
Co-authored-by: Thomas Madlener <[email protected]>

Author: jmcarcell

.clang-format

@@ -104,7 +104,7 @@ SpacesInContainerLiterals: true
 SpacesInCStyleCastParentheses: false
 SpacesInParentheses: false
 SpacesInSquareBrackets: false
-Standard:        c++17
+Standard:        c++20
 TabWidth:        8
 UseTab:          Never
 ...

.github/workflows/coverity.yml

@@ -13,7 +13,7 @@ jobs:
     - uses: cvmfs-contrib/github-action-cvmfs@v4
     - uses: aidasoft/run-lcg-view@v4
       with:
-        coverity-cmake-command: 'cmake -DCMAKE_CXX_STANDARD=17  -DENABLE_SIO=ON -DENABLE_JULIA=ON -DUSE_EXTERNAL_CATCH2=OFF ..'
+        coverity-cmake-command: 'cmake -DCMAKE_CXX_STANDARD=20  -DENABLE_SIO=ON -DENABLE_JULIA=ON -DUSE_EXTERNAL_CATCH2=OFF ..'
         coverity-project: 'AIDASoft%2Fpodio'
         coverity-project-token: ${{ secrets.PODIO_COVERITY_TOKEN }}
         github-pat: ${{ secrets.READ_COVERITY_IMAGE }}

.github/workflows/edm4hep.yaml

@@ -38,7 +38,7 @@ jobs:
             echo "::group::Build Catch2"
             cd $STARTDIR/catch2
             mkdir build && cd build
-            cmake -DCMAKE_CXX_STANDARD=17 -DCMAKE_INSTALL_PREFIX=../install -G Ninja ..
+            cmake -DCMAKE_CXX_STANDARD=20 -DCMAKE_INSTALL_PREFIX=../install -G Ninja ..
             ninja -k0 install
             export CMAKE_PREFIX_PATH=$STARTDIR/catch2/install:$CMAKE_PREFIX_PATH
             echo "::endgroup::"

.github/workflows/key4hep.yml

@@ -30,7 +30,7 @@ jobs:
           cmake -DENABLE_SIO=ON \
             -DENABLE_JULIA=OFF \
             -DCMAKE_INSTALL_PREFIX=../install \
-            -DCMAKE_CXX_STANDARD=17 \
+            -DCMAKE_CXX_STANDARD=20 \
             -DCMAKE_CXX_FLAGS=" -fdiagnostics-color=always -Werror -Wno-error=deprecated-declarations " \
             -DUSE_EXTERNAL_CATCH2=AUTO \
             -DENABLE_RNTUPLE=ON \

.github/workflows/ubuntu.yml

@@ -1,3 +1,4 @@
+
 name: ubuntu
 
 on:
@@ -13,8 +14,8 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        LCG: ["dev3/x86_64-ubuntu2204-gcc11-opt",
-              "dev4/x86_64-ubuntu2204-gcc11-opt"]
+        LCG: ["dev3/x86_64-ubuntu2404-gcc13-opt",
+              "dev4/x86_64-ubuntu2404-gcc13-opt"]
     steps:
     - uses: actions/checkout@v4
     - uses: cvmfs-contrib/github-action-cvmfs@v4
@@ -30,7 +31,7 @@ jobs:
             -DENABLE_JULIA=ON \
             -DENABLE_DATASOURCE=ON \
             -DCMAKE_INSTALL_PREFIX=../install \
-            -DCMAKE_CXX_STANDARD=17 \
+            -DCMAKE_CXX_STANDARD=20 \
             -DCMAKE_CXX_FLAGS=" -fdiagnostics-color=always -Werror -Wno-error=deprecated-declarations " \
             -DUSE_EXTERNAL_CATCH2=OFF \
             -DPODIO_SET_RPATH=ON \

CMakeLists.txt

@@ -36,7 +36,7 @@ endif()
 # ``-DCMAKE_CXX_STANDARD=<standard>`` when invoking CMake
 set(CMAKE_CXX_STANDARD 20 CACHE STRING "")
 
-if(NOT CMAKE_CXX_STANDARD MATCHES "17|20")
+if(NOT CMAKE_CXX_STANDARD MATCHES "20|23")
   message(FATAL_ERROR "Unsupported C++ standard: ${CMAKE_CXX_STANDARD}")
 endif()
 
@@ -88,10 +88,7 @@ endif()
 if(ENABLE_DATASOURCE)
   list(APPEND root_components_needed ROOTDataFrame)
 endif()
-find_package(ROOT REQUIRED COMPONENTS ${root_components_needed})
-if((ENABLE_RNTUPLE) AND (${ROOT_VERSION} VERSION_LESS 6.28.02))
-    message(FATAL_ERROR "You are trying to build podio with support for the new ROOT NTuple format, but your ROOT version is too old. Please update ROOT to at least version 6.28.02")
-endif()
+find_package(ROOT 6.28.04 REQUIRED COMPONENTS ${root_components_needed})
 
 # ROOT_CXX_STANDARD was introduced in https://github.com/root-project/root/pull/6466
 # before that it's an empty variable so we check if it's any number > 0
@@ -112,18 +109,13 @@ else()
   message(STATUS "Determined ROOT c++ standard: " ${ROOT_CXX_STANDARD})
 endif()
 
-if(ROOT_CXX_STANDARD VERSION_LESS 17)
-  message(FATAL_ERROR "You are trying to build podio against a version of ROOT that has not been built with a sufficient c++ standard. podio requires c++17 or higher")
+if(ROOT_CXX_STANDARD VERSION_LESS 20)
+  message(FATAL_ERROR "You are trying to build podio against a version of ROOT that has not been built with a sufficient c++ standard. podio requires c++20 or higher")
 endif()
 if(NOT ROOT_CXX_STANDARD VERSION_EQUAL CMAKE_CXX_STANDARD)
   message(WARNING "You are trying to build podio with a different c++ standard than ROOT. C++${CMAKE_CXX_STANDARD} was required but ROOT was built with C++${ROOT_CXX_STANDARD}")
 endif()
 
-# ROOT only sets usage requirements from 6.14, so for
-# earlier versions need to hack in INTERFACE_INCLUDE_DIRECTORIES
-if(ROOT_VERSION VERSION_LESS 6.14)
-  set_property(TARGET ROOT::Core APPEND PROPERTY INTERFACE_INCLUDE_DIRECTORIES "${ROOT_INCLUDE_DIRS}")
-endif()
 list(APPEND PODIO_IO_HANDLERS ROOT)
 
 # python setup (including python package discovery and install dir)

README.md

@@ -18,9 +18,9 @@ use a recent LCG or Key4hep stack release.
 
 On Mac OS or Ubuntu, you need to install the following software.
 
-### ROOT 6.08.06
+### ROOT 6.28.04
 
-Install ROOT 6.08.06 (or later) and set up your ROOT environment:
+Install ROOT 6.28.04 (or later) built with c++20 support and set up your ROOT environment:
 
     source <root_path>/bin/thisroot.sh
 

cmake/podioConfig.cmake.in

@@ -49,12 +49,6 @@ endif()
 if(NOT TARGET podio::podio)
   include("${CMAKE_CURRENT_LIST_DIR}/podioTargets.cmake")
   include("${CMAKE_CURRENT_LIST_DIR}/podioMacros.cmake")
-
-  # ROOT only sets usage requirements from 6.14, so for
-  # earlier versions need to hack in INTERFACE_INCLUDE_DIRECTORIES
-  if(ROOT_VERSION VERSION_LESS 6.14)
-    set_property(TARGET podio::podio APPEND PROPERTY INTERFACE_INCLUDE_DIRECTORIES "${ROOT_INCLUDE_DIRS}")
-  endif()
 endif()
 
 check_required_components(podio)

doc/frame.md

@@ -35,8 +35,8 @@ Some compilers and static code analysis tools are able to detect the accidental
 
 For putting in parameters the basic principle is very similar, with the major difference being, that for *trivial* types `getParameter` will actually return by value.
 
-For all use cases there is some `enable_if` machinery in place to ensure that only valid collections and valid parameter types can actually be used.
-These checks also make sure that it is impossible to put in collections without handing over ownership to the `Frame`.
+For all use cases there is a concept requirement to ensure that only valid collections and valid parameter types can actually be used.
+Additional checks also make sure that it is impossible to put in collections without handing over ownership to the `Frame`.
 
 ### Usage examples for collection data
 These are a few very basic usage examples that highlight the main functionality (and potential pitfalls).

doc/links.md

@@ -236,27 +236,27 @@ default handle types. This is ensured through `static_assert`s in the
 `GetDefaultHandleType` helper templates are used to retrieve the correct type
 from any `FromT` regardless of whether it is a mutable or a default handle type
 With this in mind, effectively all mutating operations on `Link`s are
-defined using [*SFINAE*](https://en.cppreference.com/w/cpp/language/sfinae)
-using the following template structure (taking here `setFrom` as an example)
+defined using the following template structure (taking here `setFrom` as an example)
 
 ```cpp
-template <typename FromU,
-          typename = std::enable_if_t<Mutable &&
-                                      std::is_same_v<detail::GetDefaultHandleType<FromU>, FromT>>>
+template <typename FromU>
+  requires(Mutable && std::is_same_v<detail::GetDefaultHandleType<FromU>, FromT> &&
+           detail::isDefaultHandleType<FromU>)
 void setFrom(FromU value);
 ```
 
-This is a SFINAE friendly way to ensure that this definition is only viable if
-the following conditions are met
-- The object this method is called on has to be `Mutable`. (first part inside the `std::enable_if`)
-- The passed in `value` is either a `Mutable` or default class of type `FromT`. (second part inside the `std::enable_if`)
+Compilation will fail unless the following conditions are met
+- The object this method is called on has to be `Mutable`.
+- The passed in `value` is either a `Mutable` or default class of type `FromT`.
 
 In some cases the template signature looks like this
 
 ```cpp
-template<bool Mut = Mutable,
-         typename = std::enable_if<Mut && Mutable>>
-void setWeight(float weight);
+template <bool Mut = Mutable>
+  requires(Mut && Mutable)
+void setWeight(float value) {
+  m_obj->data.weight = value;
+}
 ```
 
 The reason to have a defaulted `bool` template parameter here is the same as the