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++/114498] New: Consider deprecating then removing TR1 headers Date: Wed, 27 Mar 2024 12:52:25 +0000 [thread overview] Message-ID: <bug-114498-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114498 Bug ID: 114498 Summary: Consider deprecating then removing TR1 headers Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: minor Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: redi at gcc dot gnu.org Target Milestone: --- We should decide whether we want to keep std::tr1::shared_ptr etc. forever. Those headers are virtually unmaintained, and just increase testing burden. They do provide functionality that isn't otherwise available from libstdc++ in C++98/C++03 mode. But does anybody care? Is anybody stuck in C++98/C++03 mode, but also upgrading to modern GCC versions, and also relying on non-standard TR1 components that aren't actually in the C++03 standard? Can they just use Boost instead? At some point we might want to have the same discussion for <experimental/optional> and LFTSv1 components, and <experimental/filesystem too. But that seems further off.
next reply other threads:[~2024-03-27 12:52 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-27 12:52 redi at gcc dot gnu.org [this message] 2024-03-27 13:06 ` [Bug libstdc++/114498] " rguenth at gcc dot gnu.org 2024-03-27 15:20 ` redi at gcc dot gnu.org 2024-06-08 22:51 ` pinskia 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-114498-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).