public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugs at sehe dot nl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51829] decltype() deduces non-const but only in a template
Date: Thu, 12 Jan 2012 00:30:00 -0000	[thread overview]
Message-ID: <bug-51829-4-LfSXx8XpIF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51829-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51829

--- Comment #2 from Seth Heeren <bugs at sehe dot nl> 2012-01-12 00:30:36 UTC ---
To clarify, the valid code that was rejected looks like:

     auto expr = boost::spirit::qi::eps(false) | '1';

this might explain the 'strange' breaking up into e1 and e2 for the minimal
testcase. 

HTH


  parent reply	other threads:[~2012-01-12  0:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11 21:30 [Bug c++/51829] New: " bugs at sehe dot nl
2012-01-11 21:32 ` [Bug c++/51829] " bugs at sehe dot nl
2012-01-12  0:30 ` bugs at sehe dot nl [this message]
2012-01-13 12:05 ` paolo.carlini at oracle dot com
2012-05-12 23:04 ` paolo.carlini at oracle dot com
2012-05-13  3:38 ` bugs at sehe dot nl
2012-05-13  9:37 ` glisse at gcc dot gnu.org
2012-10-14 15:49 ` paolo.carlini at oracle dot com
2012-10-15 21:14 ` bugs at sehe dot nl

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-51829-4-LfSXx8XpIF@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).