public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/107135] array<T>::at() method should not be in <array> for freestanding C++
Date: Mon, 03 Oct 2022 20:26:52 +0000	[thread overview]
Message-ID: <bug-107135-4-tV3z87Q8mo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107135-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107135

--- Comment #4 from cqwrteur <unlvsur at live dot com> ---
(In reply to Jonathan Wakely from comment #3)
> Created attachment 53662 [details]
> Define <bits/functexcept.h> function for freestanding
> 
> I think I prefer this direction.

Well i guess it would only work for sub classes of logic_error and bad_alloc.

Herb Sutter said those EH will be terminate in the future even it is for
hosted? I think a consistent behavior between freestanding and hosted are very
important. Speaking the same words with different languages is just like
spelling Chinese Words for Japanese Words, they are super confusing.

  parent reply	other threads:[~2022-10-03 20:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-03 17:41 [Bug libstdc++/107135] New: " unlvsur at live dot com
2022-10-03 19:28 ` [Bug libstdc++/107135] " arsen at aarsen dot me
2022-10-03 19:40 ` redi at gcc dot gnu.org
2022-10-03 20:21 ` redi at gcc dot gnu.org
2022-10-03 20:26 ` unlvsur at live dot com [this message]
2022-10-03 20:47 ` redi at gcc dot gnu.org
2022-10-03 20:49 ` unlvsur at live dot com
2022-10-03 20:50 ` unlvsur at live dot com
2022-10-04 14:07 ` cvs-commit at gcc dot gnu.org
2022-10-04 14:28 ` 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-107135-4-tV3z87Q8mo@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).