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++/116399] C++26 text_encoding::aliases_view is not default-constructible Date: Mon, 19 Aug 2024 15:01:48 +0000 [thread overview] Message-ID: <bug-116399-4-gfI10iHtBe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-116399-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116399 --- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> --- I don't agree. Containers do: class X { using iterator = <implementation-defined>; iterator begin(); iterator end(); }; So clearly the type is the same. That's not how text_encoding::aliases_view is specified. The standard doesn't say begin() and end() return the same type, and it doesn't say aliases_view models common_range. So it's already unspecified.
next prev parent reply other threads:[~2024-08-19 15:01 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-08-17 7:50 [Bug libstdc++/116399] New: " hewillk at gmail dot com 2024-08-19 10:47 ` [Bug libstdc++/116399] " redi at gcc dot gnu.org 2024-08-19 12:43 ` redi at gcc dot gnu.org 2024-08-19 12:48 ` corentinjabot at gmail dot com 2024-08-19 12:51 ` redi at gcc dot gnu.org 2024-08-19 13:16 ` hewillk at gmail dot com 2024-08-19 13:56 ` redi at gcc dot gnu.org 2024-08-19 13:58 ` redi at gcc dot gnu.org 2024-08-19 14:11 ` hewillk at gmail dot com 2024-08-19 14:41 ` redi at gcc dot gnu.org 2024-08-19 14:50 ` hewillk at gmail dot com 2024-08-19 15:01 ` redi at gcc dot gnu.org [this message] 2024-08-19 15:02 ` 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-116399-4-gfI10iHtBe@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: linkBe 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).