For 500 or so unit tests, this can take about 30 seconds or more to run - most of that time being spent piping data to and from nearleyc. If/when I get some time, I'd like to abstract the compiler logic from nearleyc's IO and expose it as part of the library's API.
When running unit tests against grammar definitions, I currently do the following:
For 500 or so unit tests, this can take about 30 seconds or more to run - most of that time being spent piping data to and from
nearleyc
. If/when I get some time, I'd like to abstract the compiler logic fromnearleyc
's IO and expose it as part of the library's API.