On Mon, Sep 30, 2019 at 3:25 PM Paolo Carlini wrote:
>
> On 30/09/19 20:46, Jason Merrill wrote:
> > On Mon, Sep 30, 2019 at 6:54 AM Paolo Carlini
> > wrote:
> >> On 28/09/19 04:05, Jason Merrill wrote:
> >>> On 9/26/19 3:39 PM, Paolo Carlini wrote:
> +template void foo( // { dg-error "15:
Hi,
On 30/09/19 20:46, Jason Merrill wrote:
On Mon, Sep 30, 2019 at 6:54 AM Paolo Carlini wrote:
On 28/09/19 04:05, Jason Merrill wrote:
On 9/26/19 3:39 PM, Paolo Carlini wrote:
+template void foo( // { dg-error "15:template-id .foo.
used as a declarator" }
That's a strange diagnostic mess
On Mon, Sep 30, 2019 at 6:54 AM Paolo Carlini wrote:
>
> On 28/09/19 04:05, Jason Merrill wrote:
> > On 9/26/19 3:39 PM, Paolo Carlini wrote:
> >> +template void foo( // { dg-error "15:template-id .foo.
> >> used as a declarator" }
> >
> > That's a strange diagnostic message; there's nothing wron
Hi,
On 28/09/19 04:05, Jason Merrill wrote:
On 9/26/19 3:39 PM, Paolo Carlini wrote:
+template void foo( // { dg-error "15:template-id .foo.
used as a declarator" }
That's a strange diagnostic message; there's nothing wrong with using
a template-id as a declarator. Why are we even calling
On 9/26/19 3:39 PM, Paolo Carlini wrote:
+template void foo( // { dg-error "15:template-id .foo. used as a
declarator" }
That's a strange diagnostic message; there's nothing wrong with using a
template-id as a declarator. Why are we even calling grokdeclarator
when we hit EOF in the middle
Hi,
over the last weeks, while working on various batches of location
improvements (a new one is forthcoming, in case you are wondering ;) I
noticed this grokdeclarator diagnostic, one of those not exercised by
our testsuite. While constructing a testcase I realized that probably
it's better
