From: unlvsur unlvsur <unlvsur@live.com>
To: unlvsur unlvsur via Libstdc++ <libstdc++@gcc.gnu.org>
Subject: Is it possible not to use snprintf or any other stdio functionalities to throw std::logic_error in standard library containers?
Date: Sat, 15 May 2021 02:25:02 +0000 [thread overview]
Message-ID: <DM6PR05MB4697BFB3B079B97A35A72F34D62F9@DM6PR05MB4697.namprd05.prod.outlook.com> (raw)
The issue is that this will silently introduce dependency to stdio. On MinGW-w64 for example, any snprintf function call will bloat binary size for 70kb, that is even we shared linking with both msvcrt and libstdc++.
I frequently see a random bloat because of that.
By the way, it also hurts optimizations since compilers cannot merge them together.
Better just throw an exception with “vector<T> out of bounds” instead of formatting subscriptor.
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
next reply other threads:[~2021-05-15 2:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 2:25 unlvsur unlvsur [this message]
2021-05-15 8:23 ` Jonathan Wakely
2021-05-20 19:20 ` Jonathan Wakely
[not found] ` <DM6PR05MB4697628C7E6769B8FCDA1D6ED62A9@DM6PR05MB4697.namprd05.prod.outlook.com>
2021-05-20 19:35 ` Jonathan Wakely
2021-05-20 19:47 ` unlvsur unlvsur
2021-05-20 19:50 ` unlvsur unlvsur
2021-05-20 20:00 ` Jonathan Wakely
2021-05-20 19:52 ` 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=DM6PR05MB4697BFB3B079B97A35A72F34D62F9@DM6PR05MB4697.namprd05.prod.outlook.com \
--to=unlvsur@live.com \
--cc=libstdc++@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).