This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/84916] New: Tweaks to template type elision
- From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 16 Mar 2018 21:46:51 +0000
- Subject: [Bug c++/84916] New: Tweaks to template type elision
- Auto-submitted: auto-generated
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84916
Bug ID: 84916
Summary: Tweaks to template type elision
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
Priority: P3
Component: c++
Assignee: dmalcolm at gcc dot gnu.org
Reporter: dmalcolm at gcc dot gnu.org
Target Milestone: ---
In
https://www.reddit.com/r/programming/comments/84oizv/usability_improvements_in_gcc_8/dvrdyhv/
Reddit user "Liorithiel" pointed out:
> Have you considered performing elision conditionally on the length on the
> elided part? I see the benefits of changing, let say,
std::map<some<long, and, nested<type>>, std::string>
> into
std::map<[...], std::string>,
> but for me,
std::map<int, int>
> is clearer than
std::map<[...], int>.
(see the other comments downthread from thread).
I'm filing this reminder to take a look at tweaking this for gcc 9.
Maybe only elide common items if there's "more than one thing" e.g. if it's a
template itself, or is multiple args?