Greg Hurrell

Just leaving this here in case it proves useful: - Lua parser: https://github.com/rozbb/nom-lua53 - Written using nom: https://github.com/Geal/nom (a Rust-based parser-combinator library) Also: - https://blog.cloudflare.com/building-fast-interpreters-in-rust/ - https://thume.ca/2019/04/18/writing-a-compiler-in-rust/

Also, from ["The Complete Syntax of Lua"](https://www.lua.org/manual/5.1/manual.html#8): ``` chunk ::= {stat [`;´]} [laststat [`;´]] block ::= chunk stat ::= varlist `=´ explist | functioncall | do block end | while...

For comparison, here is a slightly more comprehensive example (from [the 5.3 manual](https://www.lua.org/manual/5.3/manual.html); the one above is from the 5.1 manual) — but note, Neovim uses LuaJIT, which means 5.1....

I don't have a Windows development machine but if anybody does and cares to look into this a PR would be welcome.

Heh... 😂

I suspect we can probably make `.` work by integrating with repeat.vim. For the other things, I think we should probably look at them in a case-by-case basis, starting with...

I don't have a horse in this race, but I do think a simple, opt-in heuristic might be worth looking at. One example of that would be having the ability...

I don't like the idea of having more than one way to indicate something is a feature. In fact, I'd say that I don't like the idea of having more...

> you're basically saying there can't be any breaking changes now, because tools are already locked into the current spec The spec isn't 1.0 final yet, so obviously it's not...

@jskeet > Regarding line lengths: point noted, although that's an argument in favour of "BREAKING" instead of "BREAKING CHANGE" as well. No it is not. - "BREAKING CHANGE" appears in...