LuaLS / LuaLS/lua-language-server
Missing diagnostic when calling a non-function value
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- Lua
- Estrellas
- 4.4k
- Forks
- 442
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
How are you using the lua-language-server?
Visual Studio Code Extension (sumneko.lua)
Which OS are you using?
Windows
What is the issue affecting?
Diagnostics/Syntax Checking
Expected Behaviour
LuaLS should report a diagnostic when a value whose type is known to be non-callable is called like a function.
For example, calling a number, string, boolean, or a plain table without a known __call / @overload signature should produce a warning/error, because the code will fail at runtime.
Actual Behaviour
No diagnostic is reported.
Even when the value is explicitly annotated or cast as number, LuaLS accepts the call silently.
Reproduction steps
Use the following code:
local x = 1 --[[@as number]]
x()
local y = 1
y()
---@type number
local z = 1
z()
Expected: diagnostics on x(), y(), and z().
Actual: no diagnostics are reported.
At runtime, these calls fail with an error similar to:
attempt to call a number value
Additional Notes
This is different from callable table / __call support.
I am not asking LuaLS to reject values that are explicitly annotated as callable, for example with ---@overload fun(...) or an equivalent __call signature.
The issue is about direct calls to values whose inferred or declared type is definitely not callable, such as number.
This also affects typo detection. For example, code like this can accidentally parse as a function call:
---@param name string
local function greet(name)
return "Hello " .. name "!"
end
Here name "!" is a call expression, but name is a string, so a diagnostic would be useful.
Log File
No response
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Reproduce el problema con los snippets de Lua que llaman a valores numéricos y de cadena, y luego rastrea el punto de entrada de diagnósticos o de comprobación de tipos que gestiona las expresiones de llamada. La tarea estará terminada cuando se notifiquen diagnósticos para valores definitivamente no invocables, mientras que las tablas invocables y los valores con firmas explícitas de overload o __call sigan aceptándose.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- lua
- Área
- devtools
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 65/100