From: me22 <me22.ca@gmail.com>
To: "Maik Beckmann" <beckmann.maik@googlemail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: ambiguous std::fill with character array
Date: Thu, 27 Mar 2008 22:21:00 -0000 [thread overview]
Message-ID: <fa28b9250803271521j3303a979oe9c484e93cf7202c@mail.gmail.com> (raw)
In-Reply-To: <200803272310.12137.beckmann.maik@googlemail.com>
On Thu, Mar 27, 2008 at 6:10 PM, Maik Beckmann
<beckmann.maik@googlemail.com> wrote:
> Am Donnerstag 27 März 2008 23:04:21 schrieb me22:
>
> > Bug. Your solution is likely faster than the original, but both should
> > work.
> >
> > Judging by the error message, you found a very neat case where the
> > enable_if is both true and false, thanks to the implicit conversion
> > from char const[4] to char const*, so SFINAE can't prevent either
> > instantiation, leading to the ambiguity.
>
> Ok.
>
> Will you take care of it or should I file a bug report?
>
I have nothing to do with the GCC project other than lurking on the
list, so it'd probably be best for you to post the bug, since you
found it.
~ Scott
next prev parent reply other threads:[~2008-03-27 22:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 21:11 Maik Beckmann
2008-03-27 22:04 ` me22
2008-03-27 22:10 ` Maik Beckmann
2008-03-27 22:21 ` me22 [this message]
2008-03-27 22:38 ` Maik Beckmann
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=fa28b9250803271521j3303a979oe9c484e93cf7202c@mail.gmail.com \
--to=me22.ca@gmail.com \
--cc=beckmann.maik@googlemail.com \
--cc=gcc-help@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).