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++/105344] std::source_location::curent() seemingly treated as a pure function in template specializations
Date: Wed, 02 Nov 2022 20:27:37 +0000 [thread overview]
Message-ID: <bug-105344-4-tZgV4Iw5gd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105344-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105344
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jan Polasek from comment #0)
> https://godbolt.org/z/ozf1MbG3n shows this code works fine under MSVC.
You don't try to use foo afterwards.
Once you do, MSVC will have an ICE.
try:
```
#include <source_location>
#include <utility>
template <int i, class = void> struct foo;
// Two following two specializations are different, yet gcc errors out,
// claiming they are the same.
#line 9
template <int i>
struct foo<i, std::enable_if_t<i == std::source_location::current().line()>> {
static constexpr int num = i;
};
#line 14
template <int i>
struct foo<i, std::enable_if_t<i == std::source_location::current().line()>> {
static constexpr int num = i;
};
int main(void)
{
foo<9> t;
foo<14> t;
}
```
So I don't know if this is valid or not.
prev parent reply other threads:[~2022-11-02 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 10:11 [Bug c++/105344] New: " jan at twosigma dot com
2022-11-02 20:27 ` pinskia at gcc dot gnu.org [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-105344-4-tZgV4Iw5gd@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).