From 37ea98d077a6575e7bf4259c12ce7afcd28ca3d5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Daniel=20Kr=C3=BCgler?= Date: Sat, 18 Jan 2025 14:28:20 +0100 Subject: [PATCH] New issue from Hewill: "cache_latest_view should be freestanding" --- xml/issue4189.xml | 55 +++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 xml/issue4189.xml diff --git a/xml/issue4189.xml b/xml/issue4189.xml new file mode 100644 index 0000000000..dd993bc3d3 --- /dev/null +++ b/xml/issue4189.xml @@ -0,0 +1,55 @@ + + + + +`cache_latest_view` should be freestanding +
+Hewill Kang +23 Dec 2024 +99 + + +

+`cache_latest_view` can be freestanding, but this never comes up in the discussion, which seems to be an oversight. +

+ + + + +

+This wording is relative to . +

+ +
    +

  1. Modify as indicated:

    + +
    +#define __cpp_lib_ranges_cache_latest 202411L // freestanding, also in <ranges>
+
    + +
    2. + +

  2. Modify as indicated:

    + +
    +#include <compare>              // see 
+#include <initializer_list>     // see 
+#include <iterator>             // see 
+
+namespace std::ranges {
+  […]
+  // , cache latest view
+  template<input_range V>
+    requires view<V>
+  class cache_latest_view;                                                                // freestanding
+  
+  namespace views { inline constexpr unspecified cache_latest = unspecified; }            // freestanding
+  […]
+}
+
    +
    3. +
+ + + +