Keywords trip up the parser in unexpected ways

There are many cases where keywords cause the parsing to fail:

S.obj nullable: false

fails to parse because “able” is unexpected after null

Also tangentially, quoting nullable doesn’t help

Similarly S.obj true: false fails to parse.

If I update the NullLiteral to be defined as :

NullLiteral
  /\b(null)\b/ ->
    return { $loc, token: $1 }

The nullable issue goes away, but things break if I add wordbreak boundaries to other literals like true/false. Perhaps there is a better/recommended way to handle this in hera ?

[STRd6]

Thanks for the bug report, fixed in 0.5.8!

[edemaine]

Actually, looking at true and false shows the intended solution here: append the negative lookahead assertion NonIdContinue.

Somewhat related, I notice that {true: false} parses fine, so perhaps you can adapt the explicit object literal code to the implicit object literal code.