All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bills, Jason M" <jason.m.bills@linux.intel.com>
To: openbmc@lists.ozlabs.org
Subject: Re: Time for C++20.
Date: Mon, 17 May 2021 08:18:03 -0700	[thread overview]
Message-ID: <0030cde6-7b48-2d21-1f26-629ca0ae661d@linux.intel.com> (raw)
In-Reply-To: <YHdMjAsKKA+BKW8X@heinlein>



On 4/14/2021 1:11 PM, Patrick Williams wrote:
> Hello.
> 
> Per [1], as a project we've generally committed to using the latest C++
> standard.  C++20 was released in early Sept. 2020 and already had pretty
> decent compiler support at the time it was released.  We're currently
> using GCC10 and according to [2] it has support for nearly every C++20
> feature I could see us regularly wanting to use(*).  It seems like it
> is a reasonable time for us to move on to it.
> 
> * - Except I recall seeing some mention of std::source_location being
>      useful to fix some of the issues with phosphor-logging, but that
>      won't be available until GCC11.
I just remembered and was excited to finally use std::format only to 
find that it isn't available in GCC.  Even the example code on the 
reference page fails to run: 
https://en.cppreference.com/w/cpp/utility/format/format. :)

I couldn't find anywhere that GCC has plans to include std::format. 
Does anyone know if or when std::format might be added to GCC?

> 

  parent reply	other threads:[~2021-05-17 15:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14 20:11 Time for C++20 Patrick Williams
2021-04-14 21:12 ` Bills, Jason M
2021-04-14 23:13   ` Vernon Mauery
2021-04-15 18:05     ` Patrick Williams
2021-05-17 15:18 ` Bills, Jason M [this message]
2021-05-17 18:46   ` William Kennington

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=0030cde6-7b48-2d21-1f26-629ca0ae661d@linux.intel.com \
    --to=jason.m.bills@linux.intel.com \
    --cc=openbmc@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.