On 3/26/20 11:49 PM, Patrick Palka wrote:
On Thu, 26 Mar 2020, Jason Merrill wrote:
On 3/26/20 6:36 PM, Patrick Palka wrote:
On Thu, 26 Mar 2020, Jason Merrill wrote:
On 3/26/20 5:28 PM, Patrick Palka wrote:
This adds support to detect and recover from the case where an opening
brace
On Thu, 26 Mar 2020, Jason Merrill wrote:
> On 3/26/20 6:36 PM, Patrick Palka wrote:
> > On Thu, 26 Mar 2020, Jason Merrill wrote:
> >
> > > On 3/26/20 5:28 PM, Patrick Palka wrote:
> > > > This adds support to detect and recover from the case where an opening
> > > > brace
> > > > immediately
On 3/26/20 6:36 PM, Patrick Palka wrote:
On Thu, 26 Mar 2020, Jason Merrill wrote:
On 3/26/20 5:28 PM, Patrick Palka wrote:
This adds support to detect and recover from the case where an opening brace
immediately follows the start of a requires-clause. So rather than emitting
the
error
On Thu, 26 Mar 2020, David Malcolm wrote:
> On Thu, 2020-03-26 at 17:28 -0400, Patrick Palka via Gcc-patches wrote:
> > This adds support to detect and recover from the case where an
> > opening brace
> > immediately follows the start of a requires-clause. So rather than
> > emitting the
> >
On Thu, 26 Mar 2020, Jason Merrill wrote:
> On 3/26/20 5:28 PM, Patrick Palka wrote:
> > This adds support to detect and recover from the case where an opening brace
> > immediately follows the start of a requires-clause. So rather than emitting
> > the
> > error
> >
> >error: expected
On Thu, 2020-03-26 at 17:28 -0400, Patrick Palka via Gcc-patches wrote:
> This adds support to detect and recover from the case where an
> opening brace
> immediately follows the start of a requires-clause. So rather than
> emitting the
> error
>
> error: expected primary-expression before '{'
On 3/26/20 5:28 PM, Patrick Palka wrote:
This adds support to detect and recover from the case where an opening brace
immediately follows the start of a requires-clause. So rather than emitting the
error
error: expected primary-expression before '{' token
followed by a slew of irrevelant
This adds support to detect and recover from the case where an opening brace
immediately follows the start of a requires-clause. So rather than emitting the
error
error: expected primary-expression before '{' token
followed by a slew of irrevelant errors, we now assume the user had intended
