John Haugeland

You could just add to the text "or doesn't have any javascript"

i don't really julia, but in many languages, the general approach is to make more repositories for the new data, then link them from the original, so that a downstream...

> My understanding is also that we cannot realistically use standard artifacts for all datasets that live on CRAN given their number and the fact that they can be updated...

Bump. This is extra important with the v4 migration

Oh man, I wish this had gotten merged It's really powerful, really difficult, slightly buggy, and the person who made it left github, so there's no way to ask for...

I would happily do this if I had the org permissions. Current maintainer has ignored patches for years. Lots of people including myself are heavily reliant on, and parsing, the...

Hi, I don't entirely understand this issue. I also use `peg.js` with `nyc`. I simply set the parser as an `exclude` in `.nycrc`. Are you trying to get actual coverage...

Being honest, I don't think code coverage metrics of a generated parser make sense Most of a parser is about "this isn't the grammar" A parser is machine-generated Just test...

> While yes, it is coverage of the grammar that we want, with proper coverage exposure of the parser, one should in theory be able to get full coverage of...

> While I can see how this fuzzing approach could provide some extra sanity checking, I don't see how it could replace the benefits of getting coverage out-of-the-box when a...