I have come across a situation where the preprocessor function definition value seems to be generalised to "preproc_arg." The issue lies in the fact that the entire value appears in the same color, even though it comprises multiple parts. I believe it would greatly enhance the usability and clarity of Tree-sitter-c if the value of the preprocessor could be further broken down.
Here is an example for reference:
#define CALL_FUNCTION(arg1, arg2) myFunction(arg1, arg2)
In the provided translation unit, the value is represented as "preproc_arg [0, 33] - [0, 56]" but is expected to be further broken down.
If there's a way to enhance the representation of preprocessor function definition values in Tree-sitter-c, it would be immensely beneficial for users seeking a more detailed understanding of their code.
I have come across a situation where the preprocessor function definition value seems to be generalised to "preproc_arg." The issue lies in the fact that the entire value appears in the same color, even though it comprises multiple parts. I believe it would greatly enhance the usability and clarity of Tree-sitter-c if the value of the preprocessor could be further broken down.
Here is an example for reference:
#define CALL_FUNCTION(arg1, arg2) myFunction(arg1, arg2)
In the provided translation unit, the value is represented as "preproc_arg [0, 33] - [0, 56]" but is expected to be further broken down.
If there's a way to enhance the representation of preprocessor function definition values in Tree-sitter-c, it would be immensely beneficial for users seeking a more detailed understanding of their code.