29 Feb
2024
29 Feb
'24
11:42 p.m.
On Thu, Feb 29, 2024 at 3:39 PM Vinnie Falco
As I alluded to before the review started, that is grossly unfair...
As usual, the pressing of SEND causes new valuable insights to manifest. What is important is not Boost.Parser's performance implementing a stock JSON parser, but rather that it is POSSIBLE for Boost.Parser to achieve comparable performance given enough work. Thus the question is, does Boost.Parser offer a sufficiently rich public API to allow for controlling how things are allocated and which containers are used, so that the optimizations in Boost.JSON can be replicated. Thanks