On second thought, just remove the one use of ranges::

There's only one use of `ranges::` in the codebase, and I want cppfront to compile on reasonably recent compilers. Since Apple Clang 14 only started supporting ranges in March 2023, and that seems to be the only thing stopping use of Clang 12+ even on Xcode (AFAIK), it seems more reasonable to do this and not break Xcode Clang 12+ builds of cppfront.

.github/workflows/build-cppfront.yaml

@@ -26,10 +26,10 @@ jobs:
             cxx-std: 'c++2b'
           - compiler: clang++-14
             cxx-std: 'c++2b'
-        # include:
-        #   - runs-on: macos-latest
-        #     compiler: clang++
-        #     cxx-std: 'c++20'
+        include:
+          - runs-on: macos-latest
+            compiler: clang++
+            cxx-std: 'c++20'
     runs-on: ${{ matrix.runs-on }}
     env:
       CXX: ${{ matrix.compiler }}

regression-tests/test-results/version

@@ -1,5 +1,5 @@
 
-cppfront compiler v0.3.0   Build 8C13:1859
+cppfront compiler v0.3.0   Build 8C14:0739
 Copyright(c) Herb Sutter   All rights reserved
 
 SPDX-License-Identifier: CC-BY-NC-ND-4.0

source/parse.h

@@ -3591,8 +3591,9 @@ auto function_type_node::has_postconditions() const
     -> bool
 {
     return
-        std::ranges::find_if(
-            contracts,
+        std::find_if(
+            contracts.begin(),
+            contracts.end(),
             [](auto const& e){ return *e->kind == "post"; }
         ) != contracts.end();
 }