feat(v): prefer to generate from grammar #6300
Conversation
|
Why? You should prefer to compile C, as this does not require treeitter CLI |
|
The goal is more convenience. Not keeping the generated files not in the repository but having it automatically generated at the latest development state on client side has some advantages. From what I experienced at the Also in terms of the growth of the repository size. E.g. simple changes that are part the commit history but produce a diff of ~200k lines are v-analyzer/v-analyzer#65, v-analyzer/v-analyzer#74. During early development this has more impact and the project is fairly young. So I thought it's a good way and an approach e.g. Swift is choosing. |
|
Let's wait until another maintainer of v-analyzer is confirming that generating the parser is a desired approach. |
|
As long as the parser.c is committed, you should not set this flag. It's only for repos that do not contain the generated parser. |
|
You checked the related PR at v-analyzer? It would remove the |
|
Also, there are tree-sitter projects that have |
|
Then you should make a PR to remove the flag. |
Once this is merged, we will need to adapt. But not a second sooner. |
No description provided.