Lua 5.5 introduced a new Lua syntax global x for declaring global variables.

Looking at the code:

function f()
 global y, print -- Declaring y and print as global variables
 function y()
 x = 123 --error
 print(x)
 end
end

Lua 5.5 introduced a new Lua syntax global x for declaring global variables.

Looking at the code:
...

I've added support for the new Lua 5.5 global syntax. The implementation includes:

• Added global keyword to the parser with version restriction to Lua 5.5 only
• Support for both global var1, var2 declarations and global function syntax
• Proper error reporting when used with older Lua versions
• Intelligent completion suggestions that only appear when using Lua 5.5

The parser now correctly handles the syntax from your example:

function f()
 global y, print -- Declaring y and print as global variables
 function y()
 x = 123 --error
 print(x)
 end
end

Implemented in commit 15c897a.

Lua 5.5 introduce feature: for-loop variables are read only.
Can you support check that?

Lua 5.5 introduce feature: for-loop variables are read only.
Can you support check that?

I've implemented the read-only for-loop variables check for Lua 5.5. The diagnostic now detects when you try to assign to for-loop variables and reports an error with the message "Cannot assign to for-loop variable {} (read-only in Lua 5.5)".

The implementation:

• Works for both numeric for-loops (for i = 1, 10) and for-in loops (for k, v in pairs(t))
• Only triggers when using Lua 5.5 version setting
• Includes test cases and localized error messages
• Follows the existing diagnostic patterns in the codebase

Implemented in commit aa06ff5.

There are some issues with global parsing: if it's not version 5.5, it shouldn't generate errors and should fall back to other branches directly. Users might write global = xxx, and there's no global function syntax, so don't add this during code completion.

There are some issues with global parsing: if it's not version 5.5, it shouldn't generate errors and should fall back to other branches directly. Users might write global = xxx, and there's no `glob...

Fixed the global parsing issues:

1. When version is not Lua 5.5, the parser now returns nil, true to indicate failed parse, allowing it to fallback to treating global as a regular identifier instead of generating errors
2. Removed the global function completion syntax as it doesn't exist in Lua 5.5
3. Simplified the parseGlobal() function to only handle global var1, var2 declarations

The parser now properly handles global = xxx expressions in non-5.5 versions without errors.

Implemented in commit aa69c2f.

please add this change to changelog

please add this change to changelog

Added Lua 5.5 features to the changelog including runtime version support, global keyword syntax, and read-only for-loop variables diagnostic. Implemented in commit 78942bc.

global can not be keyword, it maybe handle like goto

global can not be keyword, it maybe handle like goto

Fixed the global parsing to handle like goto - it's no longer treated as a keyword in the KeyWord table. Now global only acts as a keyword when contextually appropriate (in Lua 5.5 with proper syntax), otherwise it falls back to being treated as a regular identifier. This allows expressions like global = xxx to work correctly in all Lua versions. Implemented in commit a55f5e7.

readonly-for-loop-vars should not be a diagnostic, it should report this error at the parser stage. Can you help me reimplement it?

readonly-for-loop-vars should not be a diagnostic, it should report this error at the parser stage. Can you help me reimplement it?

I've reimplemented readonly-for-loop-vars as a parser-stage error. The implementation now detects assignments to for-loop variables during parsing and reports a SET_FOR_LOOP_VAR error with the message "Cannot assign to for-loop variable {} (read-only in Lua 5.5)". The diagnostic implementation has been removed and tests updated accordingly. Implemented in commit 686aa5f.

image

I used up all my premium requests for this month just by playing around. I'm crying.

提交太大了。希望每个功能点是一个单独的PR。
这次还是先手动改了,下个版本再试试AI

Sumneko Lua translate bot

The submission is too big. Hopefully each feature point is a separate PR.
This time I will change it manually first, and try AI in the next version

许愿未来把Lua新版本手册发给AI看,就能自动帮我实现所有功能

Sumneko Lua translate bot

Make a wish to send the new version of Lua to AI in the future, and it will automatically help me realize all functions

Maybe we should wait until 5.5 is fully released? PUC-Rio is considering some changes to the syntax