From: Zopolis0 <creatorsmithmdt@gmail.com>
To: gcc@gcc.gnu.org
Subject: Importable STL Header Units?
Date: Mon, 25 Jul 2022 19:48:28 +1000 [thread overview]
Message-ID: <CAEYL+X-KT6En79pkOiVR_ji1XkJ47k4XZvu7fz-vmNxmt_at2Q@mail.gmail.com> (raw)
Currently, when importing the standard library, one has to
separately compile each unit they want to use, which is a hindrance to the
build process and a gap in the implementation.
Is there any particular reason why gcc doesn't provide importable header
units for the standard library? Is there a timeline for this? Given that
the standard library can already be compiled into header units, is there
any particular reason why those aren't shipped with gcc?
next reply other threads:[~2022-07-25 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 9:48 Zopolis0 [this message]
2022-07-25 11:00 ` Ben Boeckel
2022-07-25 11:09 ` Jonathan Wakely
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=CAEYL+X-KT6En79pkOiVR_ji1XkJ47k4XZvu7fz-vmNxmt_at2Q@mail.gmail.com \
--to=creatorsmithmdt@gmail.com \
--cc=gcc@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).