Closed glepnir closed 1 year ago
it's not really possible to fix here, but it's something queries can resolve with match regexes given the convention for tuple ctor identifiers (single identifier that is in PascalCase)
but it also might be a function.call
? what did is change priority
for function.call
and variable
. looks like this is not correct
(call_expression
function: (identifier) @function.call
(#lua-match? @type "^[A-Z]*$"))
exactly, there's no real way to discern this - that's an LSP's job and the best one can do is make assumptions based on the ident's casing
Foo() is likely a tuple ctor, foo() a function call, make of that what you will but I could easily add that change to nvim-treesitter if desired
right. simply change property for function.call
and variable
make them less than type
will work.
well you could just use "^[A-Z][a-z0-9_]*$" for tuple ctors
Hi thanks for this parser. for a tuple struct the tree looks like not correct
in tree it's function i know it's very special , is it possible to fix ?