Date: Fri, 20 Dec 2024 10:33:46 +0000
On Thu, 19 Dec 2024 at 13:22, Jens Maurer <jens.maurer_at_[hidden]> wrote:
>
> On 19/12/2024 14.07, Nina Dinka Ranns wrote:
> >
> >
> > On Thu, 19 Dec 2024 at 11:16, Jens Maurer <jens.maurer_at_[hidden] <mailto:
> jens.maurer_at_[hidden]>> wrote:
> >
> >
> > What about the other SG22-targeted papers found via
> >
> >
> https://github.com/cplusplus/papers/issues?q=is%3Aissue+is%3Aopen+label%3Asg22
> <
> https://github.com/cplusplus/papers/issues?q=is%3Aissue+is%3Aopen+label%3Asg22
> >
> >
> > such as
> >
> > P3540R0 #embed Parameter offset
> > (#embed is definitely targeted at C++26)
> >
> > P3475R0 Defang and deprecate memory_order::consume
> > (already with CWG)
> >
> > P3352 R0 Taming the Demons (C++ version) - Undefined Behavior and
> Partial Program Correctness
> > (helps contracts, thus targeted for C++26)
> >
> > P2883 R0 offsetof Should Be A Keyword In C++26
> > (has C++26 in the title)
> >
> > ?
> >
> > If the concern is that those are not tagged as "C++26" in the paper
> tracker:
> > I've just added the C++26 label to all of the papers tagged as SG22.
> >
> >
> > Thank you, that helps.
> > I did indeed pick those who had the C++26 label first to be discussed.
> >
> > The reason other issues are not listed for this telco doesn't mean they
> won't be processed.
> > They just won't be processed in the telco I'm trying to schedule.
> >
> > Having some prioritisation would help, so if the C++xx label can't be
> used as a way of prioritising we'll have to figure out a different way of
> prioritisation.
>
> I'd suggest to prioritize those that are already with CWG (or LWG), because
> SG22 is likely to just being ignored.
>
> Then, those papers assigned to EWG, and then the rest.
>
Makes sense.
Thank you,
Nina
>
> Jens
>
>
> > Best,
> > Nina
> >
> >
> >
> > Note that paper authors can't set that the "C++xx" label in the
> paper system
> > or github, so it's nothing to depend on. Also, WG21 has a
> ship-train model,
> > so anything that's on the plate is possibly heading for the next
> train,
> > independent of C++xx labels. (That said, having a C++29 label on a
> paper
> > right now clearly indicates it's not aiming for C++26.)
> > In short, the absence of a C++xx label does not imply the paper is
> not
> > targeting C++26.
> >
> > Jens
> >
> >
> > On 18/12/2024 11.57, Nina Dinka Ranns via Liaison wrote:
> > > Hi all,
> > >
> > > We have two SG22 issues that are targeted for C++26.
> > >
> > > P3477R0 <https://wg21.link/p3477r0 <https://wg21.link/p3477r0>> There
> are exactly 8 bits in a byte (JF Bastien)
> > > P2746R0 <https://wg21.link/p2746r0 <https://wg21.link/p2746r0>> Deprecate
> and Replace Fenv Rounding Modes (Hans Boehm)
> > >
> > > Let's find a time to discuss them and give feedback from SG22
> perspective. Some possible slots are in the following doodle poll.
> > > https://doodle.com/meeting/participate/id/bD60G9qe <
> https://doodle.com/meeting/participate/id/bD60G9qe> <
> https://doodle.com/meeting/participate/id/bD60G9qe <
> https://doodle.com/meeting/participate/id/bD60G9qe>>
> > >
> > > The doodle poll is in Munich time because I was unable to figure
> out how to get it to be in UTC time. Munich time zone chosen at random. :)
> Advice welcome.
> > >
> > > Thank you,
> > > Nina
> > >
> > > _______________________________________________
> > > Liaison mailing list
> > > Liaison_at_[hidden] <mailto:Liaison_at_[hidden]>
> > > Subscription:
> https://lists.isocpp.org/mailman/listinfo.cgi/liaison <
> https://lists.isocpp.org/mailman/listinfo.cgi/liaison>
> > > Searchable archives:
> http://lists.isocpp.org/liaison/2024/12/index.php <
> http://lists.isocpp.org/liaison/2024/12/index.php>
> >
>
>
>
> On 19/12/2024 14.07, Nina Dinka Ranns wrote:
> >
> >
> > On Thu, 19 Dec 2024 at 11:16, Jens Maurer <jens.maurer_at_[hidden] <mailto:
> jens.maurer_at_[hidden]>> wrote:
> >
> >
> > What about the other SG22-targeted papers found via
> >
> >
> https://github.com/cplusplus/papers/issues?q=is%3Aissue+is%3Aopen+label%3Asg22
> <
> https://github.com/cplusplus/papers/issues?q=is%3Aissue+is%3Aopen+label%3Asg22
> >
> >
> > such as
> >
> > P3540R0 #embed Parameter offset
> > (#embed is definitely targeted at C++26)
> >
> > P3475R0 Defang and deprecate memory_order::consume
> > (already with CWG)
> >
> > P3352 R0 Taming the Demons (C++ version) - Undefined Behavior and
> Partial Program Correctness
> > (helps contracts, thus targeted for C++26)
> >
> > P2883 R0 offsetof Should Be A Keyword In C++26
> > (has C++26 in the title)
> >
> > ?
> >
> > If the concern is that those are not tagged as "C++26" in the paper
> tracker:
> > I've just added the C++26 label to all of the papers tagged as SG22.
> >
> >
> > Thank you, that helps.
> > I did indeed pick those who had the C++26 label first to be discussed.
> >
> > The reason other issues are not listed for this telco doesn't mean they
> won't be processed.
> > They just won't be processed in the telco I'm trying to schedule.
> >
> > Having some prioritisation would help, so if the C++xx label can't be
> used as a way of prioritising we'll have to figure out a different way of
> prioritisation.
>
> I'd suggest to prioritize those that are already with CWG (or LWG), because
> SG22 is likely to just being ignored.
>
> Then, those papers assigned to EWG, and then the rest.
>
Makes sense.
Thank you,
Nina
>
> Jens
>
>
> > Best,
> > Nina
> >
> >
> >
> > Note that paper authors can't set that the "C++xx" label in the
> paper system
> > or github, so it's nothing to depend on. Also, WG21 has a
> ship-train model,
> > so anything that's on the plate is possibly heading for the next
> train,
> > independent of C++xx labels. (That said, having a C++29 label on a
> paper
> > right now clearly indicates it's not aiming for C++26.)
> > In short, the absence of a C++xx label does not imply the paper is
> not
> > targeting C++26.
> >
> > Jens
> >
> >
> > On 18/12/2024 11.57, Nina Dinka Ranns via Liaison wrote:
> > > Hi all,
> > >
> > > We have two SG22 issues that are targeted for C++26.
> > >
> > > P3477R0 <https://wg21.link/p3477r0 <https://wg21.link/p3477r0>> There
> are exactly 8 bits in a byte (JF Bastien)
> > > P2746R0 <https://wg21.link/p2746r0 <https://wg21.link/p2746r0>> Deprecate
> and Replace Fenv Rounding Modes (Hans Boehm)
> > >
> > > Let's find a time to discuss them and give feedback from SG22
> perspective. Some possible slots are in the following doodle poll.
> > > https://doodle.com/meeting/participate/id/bD60G9qe <
> https://doodle.com/meeting/participate/id/bD60G9qe> <
> https://doodle.com/meeting/participate/id/bD60G9qe <
> https://doodle.com/meeting/participate/id/bD60G9qe>>
> > >
> > > The doodle poll is in Munich time because I was unable to figure
> out how to get it to be in UTC time. Munich time zone chosen at random. :)
> Advice welcome.
> > >
> > > Thank you,
> > > Nina
> > >
> > > _______________________________________________
> > > Liaison mailing list
> > > Liaison_at_[hidden] <mailto:Liaison_at_[hidden]>
> > > Subscription:
> https://lists.isocpp.org/mailman/listinfo.cgi/liaison <
> https://lists.isocpp.org/mailman/listinfo.cgi/liaison>
> > > Searchable archives:
> http://lists.isocpp.org/liaison/2024/12/index.php <
> http://lists.isocpp.org/liaison/2024/12/index.php>
> >
>
>
Received on 2024-12-20 10:33:59