public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Julien D Arques <acc.gccquestions@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Tip to reduce manual template declaration?
Date: Fri, 17 Feb 2023 08:23:09 +0100	[thread overview]
Message-ID: <CACS5Re-DO81QSqQF3GTJqjMELQ3GOF2yKcrBYKxwVGD2w6JKgw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 539 bytes --]

Hi,
I just finished a project that required to generate a static library out of
heavily templated code.

It has been a productivity nightmare and will be hard to extend if needs be.
Many "extern template XXX" in .hpp and corresponding "template XXX" in .cpp
that killed my day (many possible type combinations).

That need may happen again in a future project and I really don't want to
reiterate what I did.

Maybe modules will help but I need a solution that can be applied now.

Do we have a hack in GCC to avoid this pitfall?

Thanks,

             reply	other threads:[~2023-02-17  7:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17  7:23 Julien D Arques [this message]
2023-02-17 11:38 ` Jonathan Wakely
2023-02-17 12:02   ` Julien D Arques

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=CACS5Re-DO81QSqQF3GTJqjMELQ3GOF2yKcrBYKxwVGD2w6JKgw@mail.gmail.com \
    --to=acc.gccquestions@gmail.com \
    --cc=gcc-help@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).