public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo dot carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/42573] [C++0x] shrink_to_fit() missing
Date: Thu, 07 Jan 2010 23:18:00 -0000 [thread overview]
Message-ID: <20100107231755.9083.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42573-18622@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from paolo dot carlini at oracle dot com 2010-01-07 23:17 -------
Nope... I went through this and came to the conclusion that a fairly good
implementation has to wait for a complete resolution of N2983: the request is
non-binding thus if the move constructor can throw and the type T isn't
CopyConstructible the implementation should not do anything. Given the
subtleties wrt throwing move constructors recently surfaced, I think we'll add
this member in due course, in any case *after* having tweaked the internals of
the std containers for the other traditional member functions...
--
paolo dot carlini at oracle dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42573
next prev parent reply other threads:[~2010-01-07 23:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-01 16:05 [Bug libstdc++/42573] New: " nico at josuttis dot de
2010-01-01 17:08 ` [Bug libstdc++/42573] " paolo dot carlini at oracle dot com
2010-01-07 16:42 ` [Bug libstdc++/42573] [C++0x] " paolo dot carlini at oracle dot com
2010-01-07 16:42 ` paolo dot carlini at oracle dot com
2010-01-07 23:18 ` paolo dot carlini at oracle dot com [this message]
2010-01-08 10:05 ` jwakely dot gcc at gmail dot com
2010-01-08 10:29 ` paolo dot carlini at oracle dot com
2010-01-08 10:46 ` paolo dot carlini at oracle dot com
2010-01-08 13:01 ` paolo at gcc dot gnu dot org
2010-01-08 13:06 ` paolo dot carlini at oracle dot com
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=20100107231755.9083.qmail@sourceware.org \
--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).