v0.5.5
Fixes
- Non-literal token declaration order is now honored, same as it already was for literal tokens.
If there was a regex token declared before a literal token, and a literal token was a prefix of the regex, the parser would have always chosen the literal, which is not correct.