public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nickhuang99 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/104091] New: -std=c++20 causing meaningless error message "'auto' not allowed in alias declaration" which should be "missing template arguments after ..." Date: Tue, 18 Jan 2022 11:00:14 +0000 [thread overview] Message-ID: <bug-104091-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104091 Bug ID: 104091 Summary: -std=c++20 causing meaningless error message "'auto' not allowed in alias declaration" which should be "missing template arguments after ..." Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: nickhuang99 at hotmail dot com Target Milestone: --- considering following snippet of code: template<typename T, template<typename...>typename Template> struct Specialization{}; template<template<typename...>typename Template, typename...Args> struct Specialization<Template<Args...>, Template>{ using type=Template; }; Using -std=c++20 gives meaningless error message of "'auto' not allowed in alias declaration". While -std=c++17 or before all give correct error message: "missing template arguments after 'Template<...auto...>'". And -std=c++14 is even better with "invalid use of template-name 'Template' without an argument list". See https://godbolt.org/z/Wb9nKzcPT
next reply other threads:[~2022-01-18 11:00 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-18 11:00 nickhuang99 at hotmail dot com [this message] 2022-01-18 11:10 ` [Bug c++/104091] " pinskia at gcc dot gnu.org 2022-11-07 9:49 ` redi at gcc dot gnu.org 2022-11-07 9:53 ` redi at gcc dot gnu.org 2022-11-07 9:55 ` redi at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-104091-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).