Lua 55 support - #84
Merged
Merged
Conversation
boolangery
marked this pull request as ready for review
September 12, 2026 13:18
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Lua 5.5 support.
On the grammar side:
globaldeclarations (includingglobal functionand theglobal x *wildcard), named varargs (function f(...args)), an attribute on a wholelocallist,breakas a statement of its own rather than part ofretstat, and a stricter lexer for strings and escapes (\z, line continuations, nested long brackets).While testing this I pulled the official Lua test suite in as a corpus (
lua/luaatv5.5.1, 34 files) and ran every file through parse ->to_lua_source-> parse. All of them parsed, but the printer turned out to have a handful of bugs that only show up on real-world code:- -2came out as--2, i.e. a comment\zcontinuations, changing the string's actual valueprint"x"andf{...}were normalised toprint("x")andf({...})All four are fixed. The corpus round trip is now exact: same tree, every comment preserved, and printing is a fixpoint.