Tim Radvan
Tim Radvan
I've published 0.5.1. :+1:
It's not something we've thought about. I haven't checked in detail, but I would guess about half of Moo's source code deals with compilation. The other half is used at...
Just for fun, [here's a Gist](https://gist.github.com/tjvr/7e640d7ec669e6da03b8dec05aa2f983) which provides a silly (albeit working) approach to compiling a Moo lexer. It's silly because it extracts the `Lexer` and `LexerIterator` class definitions from...
> Is there a reason why `charCodeAt` was chosen? Benchmarks at the time showed that it was slightly faster. It's certainly possible that's changed.
Hey! You can see more context on this change here: #85
Thanks for sharing!
Ooh, that's surprising!
If someone wants to raise a PR which updates `reEscape` (or whatever the function’s called), that would be great.
Hi! I'm glad you've Moo and Nearley useful 😊 What is the exact use-case you're thinking about? Case-insensitive keywords? Sent with GitHawk
When just keywords are case-insensitive, using a [custom type transform](https://github.com/no-context/moo/pull/78#issuecomment-422865656) is my favourite solution. ```js const caseInsensitiveKeywords = defs => { const keywords = moo.keywords(defs) return value => keywords(value.toLower()) }...