matt rice

Well, I went ahead and added the railroad diagram example, this is mostly here to provide motivation, because the example was originally intended to show errorrs, the yacc file errors...

I went ahead and created a simpler PR with dustbins the Analysis and extra builder stuff, we could close this one if you'd rather start from that?

Indeed

Interesting question, I know that if it can be retained that behavior being optional seems necessary. my nimbleparse_lsp project generally should assume files start in the `Initial` state, and calls...

Edit: I think I see now what I was missing in my comment below, and what you were getting at in your comment above. The tricky evaluation order at construction...

I pushed a commit here, based on trying to get this working in comments example if it helps, but most of it is mentioned in my review. https://github.com/ratmice/grmtools/commit/67a57c6137a857ca13a3164590ad65d9c1c8df9d

I guess, I have one minor question that isn't quite about this patch the example, *lrpar/examples/start_states/comment.y* Wondering if it is intended, or if it would be better to include epsilon...

@SMartinScottLogic I believe that adding the `Option`, is for the following cases, where it can be none ``` // On receiving 'a' clear the implicit INITIAL state from the stack...

Going to break my comment in the above PR out here: The PR above fixed some of these issues, but probably not enough for CJK. I imagine what is needed...

@torkleyy I'm not really familiar with the serde code base, so could be misunderstanding, however it looks to me like it just serializes it as a struct `range` with fields...