public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109169] Feature request: Allow omitted template prompts
Date: Sat, 18 Mar 2023 01:40:35 +0000	[thread overview]
Message-ID: <bug-109169-4-LQflaDFTl0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109169-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109169

--- Comment #12 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Right and I am saying it is hard to support in a parser.
That is exactly why the language requires the template keyword here is to
distinguish and help out the parser.
Basically I am saying the whole point of template here is to help the parser
out to figure out what it should be next otherwise it cannot figure out. How
msvc implements without it, I don't know and really don't care.

  parent reply	other threads:[~2023-03-18  1:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17  4:36 [Bug c++/109169] New: " steve_green at qq dot com
2023-03-17  4:41 ` [Bug c++/109169] " steve_green at qq dot com
2023-03-17  5:05 ` pinskia at gcc dot gnu.org
2023-03-17  5:06 ` pinskia at gcc dot gnu.org
2023-03-17  5:29 ` pinskia at gcc dot gnu.org
2023-03-17  5:30 ` pinskia at gcc dot gnu.org
2023-03-17  5:30 ` pinskia at gcc dot gnu.org
2023-03-17 15:13 ` steve_green at qq dot com
2023-03-17 15:16 ` steve_green at qq dot com
2023-03-17 16:35 ` pinskia at gcc dot gnu.org
2023-03-18  1:19 ` steve_green at qq dot com
2023-03-18  1:26 ` pinskia at gcc dot gnu.org
2023-03-18  1:30 ` steve_green at qq dot com
2023-03-18  1:40 ` pinskia at gcc dot gnu.org [this message]
2023-03-18  2:15 ` pinskia at gcc dot gnu.org
2023-03-18  2:21 ` steve_green at qq dot com

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-109169-4-LQflaDFTl0@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: link
Be 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).