klondikedragon

@CosmicPangolin - How does this relate to what is being proposed in PR #176? This draft PR was focused on passing a custom value to the widget builder for a...

@petee-d - I'm very interested in trying out your prototype parser generator and offering some feedback how it works for my use case, and helping if I can with any...

@petee-d -- that's awesome! I will try out this experimental branch and report back with the results. It might take me a few days. I'll share the perf/test-suite results and...

@petee-d - I'm working through it and have it generating the parser code from the grammar. Note that in the older version of participle about 40 of my test cases...

@petee-d - the results are pretty incredible for their speedup, both in wall clock time, CPU time, and total allocations saved... I ran various test runs as well as did...

P.S. using the pooled PeekingLexer is easy enough, and `Upgrade` is still available if using a pool isn't desired: ```golang data := &aeData{} stringLexer, _ := aelexer.Lexer.(lexer.StringDefinition) lex, err :=...

oops LOL, sorry had the input size off by a factor of 10x in my previous post, the input size in above tests was 25 MB, not 250 MB. Still...

@petee-d -- there has been some good progress on getting the codegen lexer into shape, it now follows the pattern suggested by #264 to serialize the lexer definition into JSON...

@alecthomas - This is a nice separation to have! I've tested the update in bfe7c69, it looks like there is one more issue in the code generated from the serialized...

@alecthomas - here's a one-liner fix so the generated lexer code with multiple states will now compile: https://github.com/alecthomas/participle/pull/268 I'm working on some tests to add that will highlight some of...