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++/104319] better error message for parsing error when >= or >> ends a template variable.
Date: Thu, 03 Feb 2022 20:01:42 +0000	[thread overview]
Message-ID: <bug-104319-4-aYfI0GdHys@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104319-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from qingzhe huang <nickhuang99 at hotmail dot com> ---
Here I have another test case. It involves an anonymous template argument which
confuses me for a lot at the time which clang is doing a great job to clarify
the reason for me.

https://www.godbolt.org/z/YGfMncGeW

template <typename T=int, 
    std::enable_if_t<std::is_integral<T>::value, 
    bool>=true   //there should be a space in ">="
    >  
struct TestStruct{};

  parent reply	other threads:[~2022-02-03 20:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01  0:47 [Bug c++/104319] New: "parse error of template argument list" due to missing space in ">==", a better error message should be given nickhuang99 at hotmail dot com
2022-02-01  0:52 ` [Bug c++/104319] better error message for parsing error when >= ends a template variable pinskia at gcc dot gnu.org
2022-02-02 21:30 ` nickhuang99 at hotmail dot com
2022-02-02 21:36 ` [Bug c++/104319] better error message for parsing error when >= or >> " pinskia at gcc dot gnu.org
2022-02-02 21:48 ` jakub at gcc dot gnu.org
2022-02-02 21:56 ` pinskia at gcc dot gnu.org
2022-02-03  1:45 ` nickhuang99 at hotmail dot com
2022-02-03 10:41 ` jakub at gcc dot gnu.org
2022-02-03 11:13 ` jakub at gcc dot gnu.org
2022-02-03 15:40 ` jakub at gcc dot gnu.org
2022-02-03 20:01 ` nickhuang99 at hotmail dot com [this message]
2022-02-08 14:01 ` jakub at gcc dot gnu.org
2022-04-29 11:51 ` cvs-commit at gcc dot gnu.org
2022-04-29 11:52 ` jakub 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-104319-4-aYfI0GdHys@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).