public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nathanieloshead at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113405] Can't access member type alias of concept-constrained class template specialization in global module fragment via alias template in different module
Date: Fri, 19 Jan 2024 03:38:41 +0000	[thread overview]
Message-ID: <bug-113405-4-H4J2usRmUE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113405-4@http.gcc.gnu.org/bugzilla/>

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

Nathaniel Shead <nathanieloshead at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nathanieloshead at gmail dot com

--- Comment #4 from Nathaniel Shead <nathanieloshead at gmail dot com> ---
The issue seems to be that 'depset::hash::add_specializations' only adds the
first of a set of constrained specialisations that use the same arguments. This
comes down to the fact that the 'type_specializations' hashset is only hashed
on the base template and the provided arguments: differently constrained
specialisations just aren't added.

Other parts of the dependency walker seem to handle this OK, by walking the
DECL_TEMPLATE_SPECIALIZATIONS list, but not the base 'specialization_add'
function.

I'm not entirely sure yet what the best way to approach solving this is.

  parent reply	other threads:[~2024-01-19  3:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 19:41 [Bug c++/113405] New: " eddiejnolan at gmail dot com
2024-01-15 19:51 ` [Bug c++/113405] " pinskia at gcc dot gnu.org
2024-01-15 21:33 ` eddiejnolan at gmail dot com
2024-01-15 22:20 ` eddiejnolan at gmail dot com
2024-01-19  3:38 ` nathanieloshead at gmail dot com [this message]
2024-01-25  3:20 ` cvs-commit at gcc dot gnu.org
2024-01-27 10:19 ` nshead 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-113405-4-H4J2usRmUE@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).