Re: [PATCH 4/1] c++: More precise tracking of potentially unstable satisfaction

2020-12-17 Thread Jason Merrill via Gcc-patches
On 12/16/20 6:24 PM, Patrick Palka wrote: On Wed, 16 Dec 2020, Jason Merrill wrote: On 12/14/20 3:29 PM, Patrick Palka wrote: On Mon, 14 Dec 2020, Jason Merrill wrote: On 12/14/20 1:07 PM, Patrick Palka wrote: This makes tracking of potentially unstable satisfaction results more precise by

Re: [PATCH 4/1] c++: More precise tracking of potentially unstable satisfaction

2020-12-16 Thread Patrick Palka via Gcc-patches
On Wed, 16 Dec 2020, Jason Merrill wrote: > On 12/14/20 3:29 PM, Patrick Palka wrote: > > On Mon, 14 Dec 2020, Jason Merrill wrote: > > > > > On 12/14/20 1:07 PM, Patrick Palka wrote: > > > > This makes tracking of potentially unstable satisfaction results more > > > > precise by recording the sp

Re: [PATCH 4/1] c++: More precise tracking of potentially unstable satisfaction

2020-12-16 Thread Jason Merrill via Gcc-patches
On 12/14/20 3:29 PM, Patrick Palka wrote: On Mon, 14 Dec 2020, Jason Merrill wrote: On 12/14/20 1:07 PM, Patrick Palka wrote: This makes tracking of potentially unstable satisfaction results more precise by recording the specific types for which completion failed during satisfaction. We now r

Re: [PATCH 4/1] c++: More precise tracking of potentially unstable satisfaction

2020-12-14 Thread Patrick Palka via Gcc-patches
On Mon, 14 Dec 2020, Jason Merrill wrote: > On 12/14/20 1:07 PM, Patrick Palka wrote: > > This makes tracking of potentially unstable satisfaction results more > > precise by recording the specific types for which completion failed > > during satisfaction. We now recompute a satisfaction result o

Re: [PATCH 4/1] c++: More precise tracking of potentially unstable satisfaction

2020-12-14 Thread Jason Merrill via Gcc-patches
On 12/14/20 1:07 PM, Patrick Palka wrote: This makes tracking of potentially unstable satisfaction results more precise by recording the specific types for which completion failed during satisfaction. We now recompute a satisfaction result only if one of these types has been completed since the

[PATCH 4/1] c++: More precise tracking of potentially unstable satisfaction

2020-12-14 Thread Patrick Palka via Gcc-patches
This makes tracking of potentially unstable satisfaction results more precise by recording the specific types for which completion failed during satisfaction. We now recompute a satisfaction result only if one of these types has been completed since the last time we computed the satisfaction resul