public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Carlini <paolo.carlini@oracle.com>
To: "François Dumont" <frs.dumont@gmail.com>,
	"libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch] libstdc++/61143 make unordered containers usable after move
Date: Thu, 15 May 2014 20:31:00 -0000	[thread overview]
Message-ID: <5375237D.6080909@oracle.com> (raw)
In-Reply-To: <53752198.1030705@gmail.com>

Hi,

On 05/15/2014 10:20 PM, François Dumont wrote:
> Hi
>
>     Here is a proposal to fix PR 61143. As explained in the PR I 
> finally prefer to leave the container in a valid state that is to say 
> with a non zero number of bucket, that is to say 1, after a move. This 
> bucket is stored directly in the container so not allocated to leave 
> the move operations noexcept qualified. With this evolution we could 
> even make the default constructor noexcept but I don't think it has 
> any interest.
Well, FWIW my opinion (I didn't follow the issue in detail), I think it 
would be a very nice improvement, not only because of the noexcept, but 
because of the avoided dynamic memory allocation, thus performance. I'm 
sure many other implementors agree ;)

Paolo.

  reply	other threads:[~2014-05-15 20:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-15 20:20 François Dumont
2014-05-15 20:31 ` Paolo Carlini [this message]
2014-05-15 20:52 ` Jonathan Wakely
2014-05-19 20:27   ` François Dumont
2014-05-20 19:36     ` Jonathan Wakely
2014-05-20 20:37       ` François Dumont

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=5375237D.6080909@oracle.com \
    --to=paolo.carlini@oracle.com \
    --cc=frs.dumont@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@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).