<div dir="ltr">this is happening now<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Sep 11, 2024 at 12:27 AM Tom Honermann via SG16 &lt;<a href="mailto:sg16@lists.isocpp.org">sg16@lists.isocpp.org</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u>

  
    
  
  <div>
    <p>This is your friendly reminder that this meeting is taking place
      tomorrow.</p>
    <p>Tom.<br>
    </p>
    <div>On 9/9/24 12:56 PM, Tom Honermann via
      SG16 wrote:<br>
    </div>
    <blockquote type="cite">
      
      <p>SG16 will hold a meeting on Wednesday, September 11th, at 19:30
        UTC (<a href="https://www.timeanddate.com/worldclock/converter.html?iso=20240911T193000&amp;p1=1440&amp;p2=tz_pdt&amp;p3=tz_mdt&amp;p4=tz_cdt&amp;p5=tz_edt&amp;p6=tz_cest" target="_blank">timezone conversion</a>).</p>
      <p>The agenda follows.</p>
      <ul>
        <li><a href="https://wg21.link/p2319r0" target="_blank">P2319R0:
            Prevent path presentation problems</a>.<br>
        </li>
        <li><a href="https://wg21.link/p2019r6" target="_blank">P2019R6:
            Thread attributes</a>.<br>
        </li>
        <li><a href="https://wg21.link/p3364r0" target="_blank">P3364R0:
            Remove Deprecated u8path overloads From C++26</a>.<br>
        </li>
      </ul>
      <p>P2319R0 is a new paper courtesy of Victor that seeks to resolve
        some ambiguous encoding issues with <font face="monospace">std::filesystem::path</font>.
        It proposes to deprecate and replace the existing <font face="monospace">string()</font> member function with new <font face="monospace">display_string()</font> and <font face="monospace">system_string()</font> member functions with
        clear encoding specifications. Similar replacements are proposed
        for the existing <font face="monospace">generic_string()</font>
        member function. Note that these ambiguous encoding issues are
        not present for the <font face="monospace">u8</font>, <font face="monospace">u16</font>, and <font face="monospace">u32</font>
        prefixed variants of these functions; we can discuss whether
        similar concerns are present for <font face="monospace">wstring()</font>
        and <font face="monospace">generic_wstring()</font>. We&#39;ll
        review the paper and potentially poll forwarding it.</p>
      <p>P2019R6 has been around for a while but has not previously been
        reviewed by SG16. The only concern for SG16 to weigh in on is
        the handling of thread names. See the &quot;Threads have a name&quot; and
        &quot;Constraints&quot; sections for background information and the
        proposed wording for the <font face="monospace">thread::name_hint</font>
        class. As proposed, thread names may be specified via <font face="monospace">std::basic_string_view&lt;char&gt;</font> or
        <font face="monospace">std::basic_string_view&lt;char8_t&gt;</font>;
        fully portable code will therefore be constrained to characters
        from the <i>basic literal character set</i>. No requirements
        for handling of transcoding issues or ill-formed encoded names
        are specified.</p>
      <p>P3364R0 has not been previously reviewed by SG16, but it split
        from <a href="https://wg21.link/p2863r0" target="_blank">P2863R0
          (Review Annex D for C++26)</a> which we did review during the
        <a href="https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#may-24th-2023" target="_blank">2023-05-24 SG16 meeting</a>. <a href="https://wg21.link/lwg3840" target="_blank">LWG
          3840</a> was previously filed to undeprecate <font face="monospace">std::filesystem::u8path()</font>. SG16 did
        not review the LWG issue; LEWG found no consensus for it during
        the <a href="https://wiki.edg.com/bin/view/Wg21telecons2023/LWG3840" target="_blank">2023-01-10 LEWG meeting</a>. A poll in
        SG16 for <a href="https://wg21.link/p2139r2" target="_blank">P2139R2 (Reviewing Deprecated
          Facilities of C++20 for C++23)</a> during the <a href="https://wg21.link/p2139r2" target="_blank">2020-07-22
          SG16 meeting</a> had consensus for removal of <font face="monospace">std::filesystem::u8path</font>; see the
        discussion of D.23 (Deprecated filesystem path factory functions
        [depr.fs.path.factory]). The poll taken then is copied below. <br>
      </p>
      <ul dir="auto">
        <li><strong>Poll: Does SG16 object to removal of the deprecated
            filesystem path factory functions in D.23
            [depr.fs.path.factory]?</strong>
          <ul dir="auto">
            <li>
              <p dir="auto">Attendees: 9</p>
              <table>
                <thead> <tr>
                    <th align="right">Yes</th>
                    <th align="right">No</th>
                  </tr>
                </thead> <tbody>
                  <tr>
                    <td align="right">0</td>
                    <td align="right">9</td>
                  </tr>
                </tbody>
              </table>
            </li>
            <li>
              <p dir="auto">Consensus is no objection.</p>
            </li>
          </ul>
        </li>
      </ul>
      <p>Since this poll was taken four years ago, it makes sense to
        re-poll it for the new paper. We&#39;ll discuss any new information
        anyone has to offer and likely poll effectively the same
        question.<br>
      </p>
      <p>Tom.<br>
      </p>
      <br>
      <fieldset></fieldset>
    </blockquote>
  </div>

-- <br>
SG16 mailing list<br>
<a href="mailto:SG16@lists.isocpp.org" target="_blank">SG16@lists.isocpp.org</a><br>
<a href="https://lists.isocpp.org/mailman/listinfo.cgi/sg16" rel="noreferrer" target="_blank">https://lists.isocpp.org/mailman/listinfo.cgi/sg16</a><br>
</blockquote></div>

