lua-language-server
lua-language-server copied to clipboard
more emmylua enhancements
(it's okay to close this if they're not possible, just wondering if they're possible)
- (if possible) support for nice highlighting for
ffi.cdef([[]]), not just the version without parens- (edit: i don't think it's reasonable, seems like it's the builtin highlighting that's doing this)
- [ ] better typechecking in general? examples:
--- @class foo
--- @class bar
--- @param foo foo
local function fn(foo)
end
--- @param foos foo[]
local function fn2(foos)
end
local f --- @type foo
local b --- @type bar
fn(f) -- ok
fn(b) -- error
fn({ f }) -- ok (incorrect)
fn2({ f }) -- ok
fn2(f) -- ok (incorrect)
fn2(b) -- ok (incorrect)
- [ ]
@classsuppresses "global variable in lowercase initial" warning:
--- @class foo
function f()
end
- [ ] disallowing assigning decimal literals to integer variables, and numbers to different numbers (it already does this between string/number/table/string literals/integer literals etc.):
- [ ] i guess the real issue is not having decimal literal types?
--- @type integer
local foo = 1.1
--- @type 10
local foo = 1.1 -- this should error at least
- [ ] disallowing comparisons between incompatible types
- i understand this may be hard, but imo it's useful even in a simple form - e.g. checking if unions have no members that are compatible with each other (somehow...?)
- in my specific case it's just between
string|string[]andnumberso even just handling it only for primitives and arrays would be quite helpful
- in my specific case it's just between
- i understand this may be hard, but imo it's useful even in a simple form - e.g. checking if unions have no members that are compatible with each other (somehow...?)
- [ ] recursive types (not necessarily generic) - in my case i have an
@alias tree_node table<string, tree_leaf | tree_node>- i've seen #1161 which seems to imply that recursive generics are too complex - not sure if this applies to normal types
- [ ] allow
@type my_function_aliasas an alternative to@param+@return- this may be useful for e.g. request handlers for a web framework
fun(req: request, res: response): nil - it seems to kind of work for
local foo = functionandlocal function foo. doesn't seem to work forreturn function- by "kind of work" - the type of the variable seems to be fine, but it doesn't copy the argument types to the function definition:
- this may be useful for e.g. request handlers for a web framework
--- @type fun(a: integer, b: integer): nil
local function foo(a, b)
-- ^ ^ a: any, b: any
end
- [ ] check for missing properties - for example this currently shows no warnings:
--- @type { a: number, b: string }
local foo = {}
- i understand that this may be difficult to do in some cases, but like above, i think even partial support (comparing type to shape at the end of scope, or type at
return, etc) would go a long way
(added a new suggestion)
@classsuppresses "global variable in lowercase initial" warning:
Do you want ---@class do not suppress warnings?
on second thought, i guess it depends? so maybe an option may be the way to go here... or just treat it as [wontfix]
it's just something i noticed, i usually use modules so in my case at least, there should never ever be global variables
on second thought, i guess it depends? so maybe an option may be the way to go here... or just treat it as [wontfix]
it's just something i noticed, i usually use modules so in my case at least, there should never ever be global variables
You can try to color global variables with striking color with server on latest master:
// color global variables to red
"editor.semanticTokenColorCustomizations": {
"rules": {
"variable.global": "#ff0000"
}
}
It can also set font style.
- retaining flow typing for declarations with initializers:
--- @type foo | nil local x x = { foo = 1 } x.foo -- works --- @type foo | nil local x = { foo = 1 } x.foo -- need check nil (| nil overrides flow typing from the initializer)
Won't fix
- [ ]
@classsuppresses "global variable in lowercase initial" warning:--- @class foo function f() end
As design
[ ] recursive types (not necessarily generic) - in my case i have an
@alias tree_node table<string, tree_leaf | tree_node>
- i've seen Generics referencing generics #1161 which seems to imply that recursive generics are too complex - not sure if this applies to normal types
Alias need to be expanded, so I can not support recursive alias.
disallowing assigning decimal literals to integer variables, and numbers to different numbers (it already does this between string/number/table/string literals/integer literals etc.):
- [ ] i guess the real issue is not having decimal literal types?
--- @type integer local foo = 1.1 --- @type 10 local foo = 1.1 -- this should error at least
You need set Lua.type.castNumberToInteger to false