You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have read all the tree-sitter docs if it relates to using the parser
I have searched the existing issues of tree-sitter-c
Tree-Sitter CLI Version, if relevant (output of tree-sitter --version)
No response
Describe the bug
Using
inttypedeffn_typdef(constchar*args);
like syntax to define a function typedef results in the typedef keyword being highlighted as a variable and an error in the syntax tree.
:Inspect in neovim
:InspectTree
This syntax is relatively obscure but is valid and so should be highlighted correctly.
Steps To Reproduce/Bad Parse Tree
Make a file which uses function typedef syntax ReturnT typdef TypeName(args);
Now the typedef will by incorrectly represented in the tree.
Expected Behavior/Parse Tree
The tree should probably use keyword.type.c like it usually does for typedefs.
Repro
// Example code that causes the issueinttypedeffn_typdef(constchar*args);
The text was updated successfully, but these errors were encountered:
Did you check existing issues?
Tree-Sitter CLI Version, if relevant (output of
tree-sitter --version
)No response
Describe the bug
Using
like syntax to define a function typedef results in the typedef keyword being highlighted as a variable and an error in the syntax tree.
:Inspect in neovim
:InspectTree
This syntax is relatively obscure but is valid and so should be highlighted correctly.
Steps To Reproduce/Bad Parse Tree
ReturnT typdef TypeName(args);
Expected Behavior/Parse Tree
The tree should probably use keyword.type.c like it usually does for typedefs.
Repro
The text was updated successfully, but these errors were encountered: