From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Ed Smith-Rowland <3dw4rd@verizon.net>
Cc: Spencer Collyer <spencer@spencercollyer.plus.com>,
"libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: Status of P0645 (std::format) in libstdc++
Date: Sun, 16 May 2021 08:24:23 +0100 [thread overview]
Message-ID: <CAH6eHdQXw-44hwx+_d_A7c18xg_6agA2sWqksy5kyDGX2nLj+w@mail.gmail.com> (raw)
In-Reply-To: <41080801-18f7-dd92-002e-0fc3c30d726d@verizon.net>
On Sun, 16 May 2021, 03:29 Ed Smith-Rowland, <3dw4rd@verizon.net> wrote:
> On 5/15/21 9:27 AM, Jonathan Wakely via Libstdc++ wrote:
> > On Sat, 15 May 2021, 12:10 Spencer Collyer, <
> spencer@spencercollyer.plus.com>
> > wrote:
> >
> >> Firstly, I hope it is OK to ask questions like the following on this
> list.
> >>
> > Yes, totally fine!
> >
> >
> >
> >> I'm wondering what the status of P0645 in libstdc++ is at the moment?
> This
> >> is the proposal that introduces the std::format text formatting library
> in
> >> C++20.
> >>
> >> I've checked the page
> >>
> https://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.2020
> .
> >> The line for that proposal just mentions the SD 6 feature test macro
> check
> >> to see if it is supported. Is it being worked on at present?
> >>
> >
> > No, not that I'm aware of.
> >
> > For now, the best option is to use the fmt library from GitHub.
>
> I was looking into this (not that I have time) and decided that grabbing
> fmt is the best way forward for libstdc++ if the licensing could work.
>
Maybe, although an independent re-implementation of the spec has big
advantages for the quality of the spec.
prev parent reply other threads:[~2021-05-16 7:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 10:12 Spencer Collyer
2021-05-15 13:27 ` Jonathan Wakely
2021-05-16 2:28 ` Ed Smith-Rowland
2021-05-16 7:24 ` Jonathan Wakely [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=CAH6eHdQXw-44hwx+_d_A7c18xg_6agA2sWqksy5kyDGX2nLj+w@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=3dw4rd@verizon.net \
--cc=libstdc++@gcc.gnu.org \
--cc=spencer@spencercollyer.plus.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).