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++/103923] is_invocable<const T &, ...> inexplicably fails
Date: Thu, 06 Jan 2022 09:23:15 +0000	[thread overview]
Message-ID: <bug-103923-4-bZmS0Q2fdO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103923-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The instantiation of unordered_map<K, int, H> instantiates this alias:

  template<typename _Tp, typename _Hash>
    using __cache_default
      =  __not_<__and_<// Do not cache for fast hasher.
                       __is_fast_hash<_Hash>,
                       // Mandatory to have erase not throwing.
                       __is_nothrow_invocable<const _Hash&, const _Tp&>>>;

That causes the instantiations of is_invocable<const H&, const K&> before the
types are complete, which gives the wrong answer. Then the value of that trait
is memoized by the compiler, and remains false when printed out in main().

I think this is technically undefined behaviour, because the standard says that
it's undefined to instantiate std::unordered_map (and most templates in
namespace std) with incomplete types. A nested class is not complete until the
enclosing class is complete.

  parent reply	other threads:[~2022-01-06  9:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-05 23:16 [Bug c++/103923] New: " jengelh at inai dot de
2022-01-05 23:19 ` [Bug libstdc++/103923] " pinskia at gcc dot gnu.org
2022-01-06  9:23 ` redi at gcc dot gnu.org [this message]
2022-01-06  9:31 ` redi at gcc dot gnu.org
2022-01-06  9:37 ` redi at gcc dot gnu.org
2022-01-06  9:39 ` redi at gcc dot gnu.org
2022-01-06  9:46 ` redi at gcc dot gnu.org
2022-01-06 14:30 ` redi at gcc dot gnu.org
2022-01-06 14:53 ` redi at gcc dot gnu.org
2022-01-06 16:00 ` 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-103923-4-bZmS0Q2fdO@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).