From: Vinnie Falco (vinnie.falco_at_[hidden])
Date: 2020-09-23 12:22:17
On Wed, Sep 23, 2020 at 1:40 AM Gavin Lambert via Boost
<boost_at_[hidden]> wrote:
> I've walked back on that one a little bit; I now think that it's ok for
> basic_parser to do that (to retain a zero-allocation guarantee) but in
> that case it should treat numbers the same way (which it currently
> doesn't), and ideally there should be a standard slightly-higher-level
> parser that has a similar interface but does preassemble the values,
> eliminating the _part callbacks (for people who prefer ease of use over
> raw performance).
I had that originally, it was called number_parser, it was a public
interface, and it was one of the first things to go during our 3-month
journey of optimization. You can fish it out of the commit log if you
care to see it.
Thanks