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 c++/104094] Alias template shown in diagnostic with wrong template parameter name
Date: Wed, 17 Jan 2024 11:19:08 +0000	[thread overview]
Message-ID: <bug-104094-4-oR73wR991z@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104094-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|2022-01-19 00:00:00         |2024-1-17

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Another example with recent trunk:

In file included from
/home/jwakely/src/gcc/gcc/libstdc++-v3/testsuite/std/text_encoding/requirements.cc:20:
/home/jwakely/gcc/14/include/c++/14.0.1/ranges: In function 'constexpr _Cont
std::ranges::to(_Rg&&, _Args&& ...)':
/home/jwakely/gcc/14/include/c++/14.0.1/ranges:9332:21: warning: typedef 'using
_RefT = std::ranges::range_reference_t<_Pattern>' locally defined but not used
[-Wunused-local-typedefs]
 9332 |               using _RefT = range_reference_t<_Rg>;
      |                     ^~~~~

Where does _Pattern come from? There is no _Pattern in that function template.
The source line shows it should be range_reference_t<_Rg> instead.

_Pattern is used in lazy_split_view, split_view and join_view, none of which
are used at all by `ranges::to`. Is there some has collision going on here when
the pretty printer finds names? Does it need an additional disambiguation step
if more than one name is found?

  parent reply	other threads:[~2024-01-17 11:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18 13:22 [Bug c++/104094] New: " redi at gcc dot gnu.org
2022-01-19  0:50 ` [Bug c++/104094] " pinskia at gcc dot gnu.org
2024-01-17 11:19 ` redi at gcc dot gnu.org [this message]
2024-01-20 18:46 ` pinskia at gcc dot gnu.org
2024-01-20 20:39 ` 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-104094-4-oR73wR991z@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).