On Mon, 7 Nov 2022 at 22:49, Jason Merrill wrote:
>
> On 11/7/22 12:04, Jonathan Wakely wrote:
> > On Mon, 7 Nov 2022 at 21:56, Jonathan Wakely wrote:
> >>
> >> On Mon, 7 Nov 2022 at 20:58, Jason Merrill wrote:
> >>>
> >>> Tested x86_64-pc-linux-gnu. Jonathan, what do you want to do about the
On 11/7/22 12:04, Jonathan Wakely wrote:
On Mon, 7 Nov 2022 at 21:56, Jonathan Wakely wrote:
On Mon, 7 Nov 2022 at 20:58, Jason Merrill wrote:
Tested x86_64-pc-linux-gnu. Jonathan, what do you want to do about the library
test failure?
-- >8 --
This paper is resolving the problem of
On Mon, 7 Nov 2022 at 21:56, Jonathan Wakely wrote:
>
> On Mon, 7 Nov 2022 at 20:58, Jason Merrill wrote:
> >
> > Tested x86_64-pc-linux-gnu. Jonathan, what do you want to do about the
> > library
> > test failure?
> >
> > -- >8 --
> >
> > This paper is resolving the problem of well-formed
On Mon, 7 Nov 2022 at 20:58, Jason Merrill wrote:
>
> Tested x86_64-pc-linux-gnu. Jonathan, what do you want to do about the
> library
> test failure?
>
> -- >8 --
>
> This paper is resolving the problem of well-formed C++17 code becoming
> ambiguous in C++20 due to asymmetrical operator==
Tested x86_64-pc-linux-gnu. Jonathan, what do you want to do about the library
test failure?
-- >8 --
This paper is resolving the problem of well-formed C++17 code becoming
ambiguous in C++20 due to asymmetrical operator== being compared with itself
in reverse. I had previously implemented a
