<div dir="auto">I&#39;m afraid I&#39;m going to miss this one. I&#39;ve got to meet with a tax accountant about my Dad&#39;s estate. </div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 9, 2024, 17:46 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>

  
    
  
  <div>
    <p>This is your friendly reminder that this meeting is taking place
      tomorrow.</p>
    <p>Tom.<br>
    </p>
    <p></p>
    <div>On 4/8/24 4:15 PM, Tom Honermann via
      SG16 wrote:<br>
    </div>
    <blockquote type="cite">
      
      <p>SG16 will hold a meeting on Wednesday, April 10th, at 19:30 UTC
        (<a href="https://www.timeanddate.com/worldclock/converter.html?iso=20240410T193000&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" rel="noreferrer">timezone conversion</a>).</p>
      <p><b>For those in Europe, please note that daylight savings time
          has begun, so this telecon will begin one hour later relative
          to the last SG16 telecon.</b></p>
      <p>The agenda follows.</p>
      <ul>
        <li><a href="https://wg21.link/p2758r2" target="_blank" rel="noreferrer">P2758R2:
            Emitting messages at compile time</a>.</li>
      </ul>
      <p>Though prior revisions of P2758 had an honorable mention in a
        couple of SG16 meetings last year, this will be our first formal
        review of it. The initial version of this paper was introduced
        at the same time as <a href="https://wg21.link/p2741" target="_blank" rel="noreferrer">P2741 (user-generated static_assert
          messages)</a> with significant overlap in functionality. <a href="https://wg21.link/p2741r3" target="_blank" rel="noreferrer">P2741R3</a>
        was adopted for C++26 during the Varna WG21 meeting in 2023 and
        P2758R2 has been updated to remove the overlap (at least from
        what is proposed, sections 2.1 and 4 don&#39;t appear to have been
        updated). This paper proposes a set of library functions that
        enable a custom diagnostic message to be produced as an
        informative, warning, or error message with corresponding effect
        on translation success. Please review the prior discussion of <a href="https://wg21.link/p2741r1" target="_blank" rel="noreferrer">P2741R1
          (user-generated static_assert messages)</a> during the <a href="https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#april-26th-2023" target="_blank" rel="noreferrer">2024-04-26 SG16 meeting</a> for
        context. EWG has already reviewed the proposal during the <a href="https://wiki.edg.com/bin/view/Wg21issaquah2023/NotesEWGstaticassert" target="_blank" rel="noreferrer">2023 Issaquah meeting</a>, during its <a href="https://wiki.edg.com/bin/view/Wg21telecons2024/P2758R1-EWG" target="_blank" rel="noreferrer">2024-01-31 telecon</a>, and in <a href="https://wiki.edg.com/bin/view/Wg21tokyo2024/NotesEWGP2758" target="_blank" rel="noreferrer">Tokyo</a>; further review is pending
        LEWG review. As always, we&#39;ll discuss encoding related matters
        but will try to avoid topics that are not otherwise in our
        purview. Please note that <font face="monospace">static_assert</font>,
        as updated by P2741R3, requires that the <i><a href="http://eel.is/c++draft/dcl.pre#nt:static_assert-message" target="_blank" rel="noreferrer">static_assert-message</a></i> be
        encoded in the ordinary literal encoding with use of <i><a href="http://eel.is/c++draft/lex.charset#nt:universal-character-name" target="_blank" rel="noreferrer">universal-character-name</a></i> or <i><a href="http://eel.is/c++draft/lex.ccon#nt:simple-escape-sequence" target="_blank" rel="noreferrer">simple-escape-sequence</a></i>
        restricted to the <i><a href="http://eel.is/c++draft/lex.string.uneval#nt:unevaluated-string" target="_blank" rel="noreferrer">unevaluated-string</a></i> form.</p>
      <p>We have other papers to review, but I am freshly back from
        vacation and other authors are either unavailable or I haven&#39;t
        made contact with them yet (and won&#39;t do so with such little
        notice). So, this might be a short meeting.<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" rel="noreferrer">SG16@lists.isocpp.org</a><br>
<a href="https://lists.isocpp.org/mailman/listinfo.cgi/sg16" rel="noreferrer noreferrer" target="_blank">https://lists.isocpp.org/mailman/listinfo.cgi/sg16</a><br>
</blockquote></div>

