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] New: Feature request: Allow omitted template prompts
Date: Fri, 17 Mar 2023 04:36:58 +0000 [thread overview]
Message-ID: <bug-109169-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109169
Bug ID: 109169
Summary: Feature request: Allow omitted template prompts
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: steve_green at qq dot com
Target Milestone: ---
I have a third party library that has this write up
```c++
template<class T>
template struct type_info_t{
//...
template<class U>
static constexpr bool can_convert_to=XXX;
//...
}
template<class T>
constexpr type_info_t<T>type_info{};
```
Since msvc supports such writes, the form of `type_info<T>.can_convert_to<U>`,
`compare.able<T>`, `invoke<F>.nothrow<Args... >` are written throughout the
project.
Although this is not the standard way of writing, I would expect gcc to support
such code.
next reply other threads:[~2023-03-17 4:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 4:36 steve_green at qq dot com [this message]
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
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@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).