AnyhowStep

I just made a better repro and added it to the repo above. The following should work, but fails, ``` Identifier -> %identifier # this is a comment with 1,055...

I noticed the error seemed to always reference, ``` at Parser.feed at StreamWrapper.write [as _write] ``` So, I changed `stream.js` to, ```js StreamWrapper.prototype._write = function write(chunk, encoding, callback) { console.log("==...

I *think* this might be what's happening, 1. `Parser.feed("# this is a comment with ")` 2. `lexer.reset("# this is a comment with ")` 3. `lexer.next()` returns token type `comment` 4....

i decided to look at the diff of 2.20.1 and 2.11.2. I noticed this in the `nearley-language-bootstrapped.ne` file for 2.11.2, https://github.com/kach/nearley/blob/e476c6dceff5b7f72fe5fe57282e7e72bbbc8423/lib/nearley-language-bootstrapped.ne#L104-L106 Whereas 2.20.1 uses moo's lexer, https://github.com/kach/nearley/blob/6983001d85c3530f08407f955357ff6085806a66/lib/nearley-language-bootstrapped.ne#L18 So, nearley is...

I've given it some thought and I can't think of a way to fix this easily. The options are, + Remove chunking (read the whole string, then pass it to...

What if the expression is a conditional type?

Another example, from the unified library, this time, ```ts myTable.insertAndFetch( connection, //snip row ); ``` Internally, `insertAndFetch()` does something like this, ```ts connection.transactionIfNotInOne(async (connection) => { //snip insertOne() //snip fetchOne()...

This transaction behaviour may surprise users, ```ts myPool.onInsertOne.addHandler(async (event) => { console.log(event.connection.isInTransaction()); }); //snip await myTable.insertOne(connection, /*snip row*/); //prints false await myTable.insertAndFetch(connection, /*snip row*/); //prints true ``` However, I think...

Then, if we want multiplication-but-allow-null-return-type-for-nan, we can have a separate function `double.mulWithNan()` or some other such nonsense

Or maybe just not have `mulWithNan` for the unified library at all