On Tue, Jul 23, 2019 at 8:06 PM Andrew Barnert wrote:
> On Jul 23, 2019, at 18:44, Nam Nguyen wrote:
> >
> > FYI, my current proof of concept parser is at ~300 lines of code, with
> debugging trace support. Other than performance (which I don't intend to
> tackle in my library very soon), is the
On 7/24/2019 9:15 PM, Nam Nguyen wrote:
Back to my original requests to the list: 1) Whether we want to have a
(possibly private) parsing library in the stdlib, and 2) What features
it should have. I have proposed that 1) yes, such a library would be
useful, and 2) several requirements that suc
On Wed, Jul 24, 2019 at 6:40 PM Eric V. Smith wrote:
> On 7/24/2019 9:15 PM, Nam Nguyen wrote:
> > Back to my original requests to the list: 1) Whether we want to have a
> > (possibly private) parsing library in the stdlib, and 2) What features
> > it should have. I have proposed that 1) yes, suc
On Thu, Jul 25, 2019 at 12:11 PM Nam Nguyen wrote:
>
> On Wed, Jul 24, 2019 at 6:40 PM Eric V. Smith wrote:
>> For something in
>> the stdlib, I think it has to be "here are the problems to be solved,
>> now I'll design a parser to solve them".
>
>
> I gave links to CVEs and bugs in BPO. Those ar
