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++/60497] unique_ptr<T> tries to complete its type T even though it's not required to be a complete type
Date: Tue, 13 May 2014 14:30:00 -0000	[thread overview]
Message-ID: <bug-60497-4-PEttglD1yR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60497-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60497

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---
           Assignee|unassigned at gcc dot gnu.org      |redi at gcc dot gnu.org

--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This issue actually touches half the library.

Using std::bind with unique_ptr<B<A>> tries to complete A

Using unique_lock<Something<unique_ptr<B<A>>> tries to complete A

Using call_once(o, f, Something<unique_ptr<B<A>>) tries to complete A

etc. etc.

There are a few more unqualified std::get calls that I'm fixing, but most of
the problems come from using the built-in & operator, which does ADL and so
tries to complete A. That means we must use std::addressof even on internal
library types without an overloaded operator& if they have any template
arguments of user-defined types.


  parent reply	other threads:[~2014-05-13 14:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-11  3:46 [Bug c++/60497] New: " richard-gccbugzilla at metafoo dot co.uk
2014-04-14 15:33 ` [Bug libstdc++/60497] " redi at gcc dot gnu.org
2014-04-15 19:16 ` redi at gcc dot gnu.org
2014-04-27 16:37 ` redi at gcc dot gnu.org
2014-04-27 16:38 ` redi at gcc dot gnu.org
2014-05-13 11:18 ` redi at gcc dot gnu.org
2014-05-13 14:30 ` redi at gcc dot gnu.org [this message]
2014-05-13 16:50 ` redi at gcc dot gnu.org
2014-05-13 17:22 ` redi at gcc dot gnu.org
2015-06-22 14:26 ` rguenth at gcc dot gnu.org
2021-04-30 13:55 ` redi at gcc dot gnu.org
2021-04-30 14:48 ` cvs-commit 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-60497-4-PEttglD1yR@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).