Set 4389 to SG9/P2

Author: tomaszkam

xml/issue4389.xml

@@ -1,12 +1,12 @@
 <?xml version='1.0' encoding='utf-8' standalone='no'?>
 <!DOCTYPE issue SYSTEM "lwg-issue.dtd">
 
-<issue num="4389" status="New">
+<issue num="4389" status="SG9">
 <title>`ranges::for_each` possibly behaves differently from range-based `for`</title>
 <section><sref ref="[range.range]"/></section>
 <submitter>Jiang An</submitter>
 <date>28 Sep 2025</date>
-<priority>99</priority>
+<priority>2</priority>
 
 <discussion>
 <p>
@@ -29,6 +29,13 @@ implementation to tell whether a class has member `begin/end` but the correspond
 call is ill-formed with C++20 core language rules, and such determination is critical for 
 eliminating the semantic differences between `ranges::for_each` and range-for.
 </p>
+
+<note>2025-10-23; Reflector pool; Status changed: New &rarr; SG9 and P2.</note>
+<p>
+This is certainly evoluationary question and should go to LEWG/SG9.
+It would disallow having unrelated begin/end members, whilke range
+interface is provided by hidden friends.
+</p>
 </discussion>
 
 <resolution>