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++/109136] initializer_list constructor constraint and explicit conversion operator
Date: Tue, 14 Mar 2023 22:35:17 +0000	[thread overview]
Message-ID: <bug-109136-4-09fDMeyJdM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109136-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[concepts] initializer_list |initializer_list
                   |constructor constraint      |constructor constraint and
                   |should require static_cast  |explicit conversion
                   |for explicit conversion     |operator
                   |operator                    |

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This has nothing to do with concepts really:
```

#include <initializer_list>

struct foo {
explicit operator int();
};

template <class From, class To>
void f(From x)
{
  std::initializer_list<To>{ x };
}
void g()
{
  f<foo, int>(foo{});
}
```
GCC accepts the above example but clang rejects it.

  reply	other threads:[~2023-03-14 22:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 22:25 [Bug c++/109136] New: [concepts] initializer_list constructor constraint should require static_cast for " ldalessandro at gmail dot com
2023-03-14 22:35 ` pinskia at gcc dot gnu.org [this message]
2023-03-14 22:45 ` [Bug c++/109136] initializer_list constructor and " pinskia 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-109136-4-09fDMeyJdM@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).