public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "3dw4rd at verizon dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/58781] Unicode strings broken in a strange way
Date: Mon, 21 Oct 2013 18:13:00 -0000 [thread overview]
Message-ID: <bug-58781-4-Fmr84I7IS9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58781-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58781
Ed Smith-Rowland <3dw4rd at verizon dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #31061|0 |1
is obsolete| |
--- Comment #2 from Ed Smith-Rowland <3dw4rd at verizon dot net> ---
Created attachment 31064
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31064&action=edit
If decltype of user-defined lieteral of a function call could res
Question: Does the decltype problem happen with user-defined numeric literals?
Answer: No.
Question: If I call the operator""_s explicitly in decltype is there a problem?
Answer: No.
Remaining questions...
Question #1: Is this a regression? There was work for decltype(auto).
Question #2: in cp_parser_decltype_expr what path should be taken for a normal
function call?
next prev parent reply other threads:[~2013-10-21 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 8:08 [Bug c++/58781] New: " mustrumr97 at gmail dot com
2013-10-21 16:37 ` [Bug c++/58781] " 3dw4rd at verizon dot net
2013-10-21 18:13 ` 3dw4rd at verizon dot net [this message]
2013-10-21 20:25 ` 3dw4rd at verizon dot net
2013-10-30 13:32 ` redi at gcc dot gnu.org
2014-06-27 21:04 ` 3dw4rd at verizon dot net
2014-07-01 3:14 ` emsr at gcc dot gnu.org
2014-07-01 5:31 ` emsr at gcc dot gnu.org
2014-07-01 5:33 ` emsr 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-58781-4-Fmr84I7IS9@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).