public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tim at klingt dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/107894] New: [feature request] _GLIBCXX_ASSERTIONS for std::optional Date: Mon, 28 Nov 2022 10:27:51 +0000 [thread overview] Message-ID: <bug-107894-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107894 Bug ID: 107894 Summary: [feature request] _GLIBCXX_ASSERTIONS for std::optional Product: gcc Version: 12.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: tim at klingt dot org Target Milestone: --- `_GLIBCXX_ASSERTIONS` does not enable any API validation for std::optional. e.g. `operator->` translates to `address_to`: https://github.com/gcc-mirror/gcc/blob/master/libstdc%2B%2B-v3/include/std/optional#L969-L970 libc++ on the other hand has assertions that can detect invalid uses: https://github.com/llvm/llvm-project/blob/main/libcxx/include/optional#L930-L937 it would be great if libstdc++ could perform the same validation
next reply other threads:[~2022-11-28 10:27 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-28 10:27 tim at klingt dot org [this message] 2022-11-28 11:08 ` [Bug libstdc++/107894] " 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-107894-4@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).