Nelo Mitranim

We're using this linter through `golangci-lint`, mainly for the "unused parameter" check which is extremely useful. In our particular codebase, "always receives X" is always an annoyance. Would be nice...

> monitor 2 (M2) running zsh, where I call `gow run .` Requires clarification: running how? Via Terminal / iTerm2 / another VSCode window / something else? > when I...

If your Go app opens its own GUI window, you should probably clarify this, since it's uncommon for Go apps. When `gow` restarts it, does the system reopen the window...

Just found that this can be reproduced with a simpler pattern. Logging just in case. ``` main = `[` main* `]`; ``` This isn't equivalent to the example in the...

Realized that including `(~main)*` defined as `(~a|b|c)*` is equivalent to `(~(~a|b|c)*)*`. The writer can alleviate this with separate definitions: ``` main = (~any)*; any = parens|braces|ident; parens = `(` (~any)*...

Also, trying to write the following gives a NYI panic: ``` main = (~parens|braces|ident)*; parens = `(` main ~`)`; braces = `{` main ~`}`; ident = '\b[[:alpha:]_][[:alnum:]_]*\b'; ``` ``` main...

For the benefit of anyone interested, there's now a package for printing data as Go code: https://github.com/Mitranim/repr It's made mostly for code generation, producing pretty code that you would write...

Was hoping I wouldn't have to answer this question, but you got me there. I would expect it to simply override the scope specified before `=`. For example: ``` rule0{scope0}...

I'm in favor of making the SBNF syntax simple and consistent. Whichever way we declare scopes, it should be the same for literals and rules. The current approach involves different...

Duplicating this from #12 to continue the topic. > Realized that in my head, passing options to a rule is a shortcut to the following: > > ``` > outer...