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 libstdc++/107792] Output of default contract violation handler could be improved
Date: Mon, 21 Nov 2022 13:40:54 +0000 [thread overview]
Message-ID: <bug-107792-4-eFrw8juzLi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107792-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107792
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #0)
> default std::handle_contract_violation called:
N.B. The function is not in namespace std.
This seems better:
default handle_contract_violation called [default:default:NEVER]
in function f at fail.cc:1: r > 0
terminate called without an active exception
Aborted (core dumped)
We could say "[level:default role:default continue:NEVER]" instead if the
shorter form is too obscure.
Maybe instead of saying the default handler was called, we should just say a
contract was violated. That's what users actually care about, not the handler
itself:
contract violation in function f at fail.cc:1: r > 0
[level:default, role:default, continuation mode:never]
terminate called without an active exception
Aborted (core dumped)
next prev parent reply other threads:[~2022-11-21 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 11:43 [Bug libstdc++/107792] New: " redi at gcc dot gnu.org
2022-11-21 13:40 ` redi at gcc dot gnu.org [this message]
2022-11-21 17:30 ` [Bug libstdc++/107792] " pinskia at gcc dot gnu.org
2022-11-21 17:32 ` redi at gcc dot gnu.org
2022-12-23 0:51 ` cvs-commit at gcc dot gnu.org
2023-01-25 13:29 ` 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-107792-4-eFrw8juzLi@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).