public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/61374] string_view::operator string() is buggy
Date: Sun, 01 Jun 2014 17:24:00 -0000 [thread overview]
Message-ID: <bug-61374-4-vrRROp5QUM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61374-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61374
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Sun Jun 1 17:23:41 2014
New Revision: 211113
URL: http://gcc.gnu.org/viewcvs?rev=211113&root=gcc&view=rev
Log:
PR libstdc++/61374
* include/experimental/string_view (operator basic_string): Correct
order of arguments.
(to_string): Replace with member function.
Add inline specifiers. Remove unused header. Remove _S_empty_rep and
allow _M_str to be null.
* testsuite/experimental/string_view/cons/char/1.cc: Adjust to new
default constructor semantics.
* testsuite/experimental/string_view/cons/wchar_t/1.cc: Likewise.
* testsuite/experimental/string_view/operations/copy/char/1.cc: Fix
copyright dates. Remove unused header.
* testsuite/experimental/string_view/operations/copy/wchar_t/1.cc:
Likewise.
* testsuite/experimental/string_view/operations/data/char/1.cc:
Fix copyright dates. Adjust to new default constructor semantics.
* testsuite/experimental/string_view/operations/data/wchar_t/1.cc:
Likewise.
* testsuite/experimental/string_view/operations/to_string/1.cc: New.
Added:
trunk/libstdc++-v3/testsuite/experimental/string_view/operations/to_string/
trunk/libstdc++-v3/testsuite/experimental/string_view/operations/to_string/1.cc
- copied, changed from r211112,
trunk/libstdc++-v3/testsuite/experimental/string_view/operations/copy/char/1.cc
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/include/experimental/string_view
trunk/libstdc++-v3/include/experimental/string_view.tcc
trunk/libstdc++-v3/testsuite/experimental/string_view/cons/char/1.cc
trunk/libstdc++-v3/testsuite/experimental/string_view/cons/wchar_t/1.cc
trunk/libstdc++-v3/testsuite/experimental/string_view/operations/copy/char/1.cc
trunk/libstdc++-v3/testsuite/experimental/string_view/operations/copy/wchar_t/1.cc
trunk/libstdc++-v3/testsuite/experimental/string_view/operations/data/char/1.cc
trunk/libstdc++-v3/testsuite/experimental/string_view/operations/data/wchar_t/1.cc
next prev parent reply other threads:[~2014-06-01 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-31 2:21 [Bug libstdc++/61374] New: " john.salmon at deshaw dot com
2014-05-31 10:54 ` [Bug libstdc++/61374] " redi at gcc dot gnu.org
2014-05-31 10:59 ` redi at gcc dot gnu.org
2014-06-01 17:24 ` redi at gcc dot gnu.org [this message]
2014-06-01 17:25 ` redi at gcc dot gnu.org
2014-07-16 13:29 ` jakub at gcc dot gnu.org
2014-08-04 18:50 ` redi at gcc dot gnu.org
2014-08-04 18:52 ` redi 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-61374-4-vrRROp5QUM@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).