public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steve_green at qq dot com" <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 02:21:04 +0000	[thread overview]
Message-ID: <bug-109169-4-vJYAkcUuwV@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 #14 from steve02081504 <steve_green at qq dot com> ---
(In reply to Andrew Pinski from comment #13)
> See http://womble.decadent.org.uk/c++/template-faq.html#disambiguation also
> to better understand the reason why GCC implements it this way and why it is
> hard to implement this "extension" in all cases.

But I guess type_info<T>.some_class_name a; is not allowed, right?
Only in the case of decltype(type_info<T>)::name do we need to consider whether
this is a typename or a template, and in the case of type_info<T>.name this
should always be a template?

      parent reply	other threads:[~2023-03-18  2:21 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
2023-03-18  2:15 ` pinskia at gcc dot gnu.org
2023-03-18  2:21 ` steve_green at qq dot com [this message]

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-vJYAkcUuwV@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).