matt rice

I had a look through these, and it appears to me that these just want to be turned into `\"{}\"`. I.e. they are all names, etc that we wouldn't expect...

So, I believe this one can finally be closed. As the implementation has been in for a while, and the errors are now all wired up to the builders.

I'll give a go at a rough draft here, though admittedly i'm pretty terrible at writing, and working off of memory . When we introduce states to lex the first...

> ` \* "ASTERISK"` Yes, you can return a token *exactly* like that. Thanks for pointing out this omission both in what I wrote, and the existing example! There is...

@ltratt I believe it is intentional, sorry I didn't catch it earlier! Flex doesn't accept spaces between the start state, and the regular expression. It does accept leading initial spaces,...

I have only ever seen it used for embedding comments (I put some stuff in the relevant bug report). I had suggested one option there is that we ignore these...

@ltratt I realized that part of that first quoted text was being interpreted as markdown, reproduced it again below because it was omitting crucial `` so it didn't make much...

> I'm not a big fan of ignoring such lines, because I guess that some people expect this to interact with lex code? Found another section relating to the above...

Just wanted to ditto that it doesn't seem like a high priority, while perhaps not the most elegant, file watchers are possible to get working with the current API. I'd...

Curious how your think went, I was thinking about it too a bit One thing I would note is that in the [w3c gamepad api](https://www.w3.org/TR/gamepad/), doesn't appear to encode any...