this is the first part of some changes/fixes I'll make to this repo (the forthcoming ones being more grammar/scanner bug fixes) - I know this one has several contributors/more activity compared to the other upstream grammars (where it's pretty much just me maintaining it ;) ), so I'll leave this up for a bit in case anyone has questions/comments
I'll also be updating the repo secrets so we can get this grammmar published to npm and pypi :grin: I think the current CI is a little overkill - all we need to do is test that is parses the test corpus, scala3, and scala, and I've dumped all known failures into a file, so regressions can be found easily if a file outside of these fails to parse correctly
well, some good news is the scanner stack changes fixed some edit fuzzing bugs :partying_face: was trying to replicate one and I couldn't, but I managed to get another
Closes #344 Closes #384
this is the first part of some changes/fixes I'll make to this repo (the forthcoming ones being more grammar/scanner bug fixes) - I know this one has several contributors/more activity compared to the other upstream grammars (where it's pretty much just me maintaining it ;) ), so I'll leave this up for a bit in case anyone has questions/comments
I'll also be updating the repo secrets so we can get this grammmar published to npm and pypi :grin: I think the current CI is a little overkill - all we need to do is test that is parses the test corpus, scala3, and scala, and I've dumped all known failures into a file, so regressions can be found easily if a file outside of these fails to parse correctly