public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: dkm@kataplop.net
To: "Tom Tromey" <tom@tromey.com>, "David Malcolm via Gcc" <gcc@gcc.gnu.org>
Cc: "Jonathan Wakely" <jwakely.gcc@gmail.com>,
	"Pierrick Philippe" <pierrick.philippe@irisa.fr>,
	"David Malcolm" <dmalcolm@redhat.com>,
	arthur.cohen@embecosm.com, pierre-emmanuel.patry@embecosm.com
Subject: Re: Using std types and functions within GCC
Date: Fri, 15 Mar 2024 13:43:25 +0000	[thread overview]
Message-ID: <023b7230d4c8613a75a164dd77fc2e2f43ecf7db@kataplop.net> (raw)
In-Reply-To: <87r0gbk5ul.fsf@tromey.com>

March 15, 2024 at 2:00 PM, "Tom Tromey" <tom@tromey.com> wrote:
 
> > 
> > "David" == David Malcolm via Gcc <gcc@gcc.gnu.org> writes:
> > 
> 
> David> For example, there's at
> David> least one place where I'd have used std::optional, but that's C++14 and
> David> so unavailable.
> 
> FWIW, gdb had its own gdb::optional (which was really just a
> stripped-down copy of the one from libstdc++) to fill exactly this need,
> at least until we moved to C++17 this year. If you need it you could
> easily lift it from the gdb repository.
> 

Hi,

In the Rust frontend, we are using a single header implementation from https://github.com/TartanLlama/optional, until we can use something from libstdc++.

Marc

      parent reply	other threads:[~2024-03-15 13:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14 12:53 Pierrick Philippe
2024-03-14 13:28 ` Jonathan Wakely
2024-03-14 14:49   ` David Malcolm
2024-03-14 14:55     ` Jonathan Wakely
2024-03-15 13:00     ` Tom Tromey
2024-03-15 13:43     ` dkm [this message]

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=023b7230d4c8613a75a164dd77fc2e2f43ecf7db@kataplop.net \
    --to=dkm@kataplop.net \
    --cc=arthur.cohen@embecosm.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    --cc=pierre-emmanuel.patry@embecosm.com \
    --cc=pierrick.philippe@irisa.fr \
    --cc=tom@tromey.com \
    /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).