dundargoc
dundargoc
I've created [milestones](https://github.com/tree-sitter/tree-sitter/milestones) for these issues and PRs. That way we can have a centralized place to set the roadmap rather than scattered around in various issues.
@amaanq if you want we could close this to avoid duplication. Up to you though, I don't really mind either way.
https://github.com/fwcd/tree-sitter-kotlin/pull/111 has been merged. @juli1 could you confirm the problem has been fixed?
I'm not strictly against it, but this feels like a low-value suggestion tbh. This file is rarely changed IIUC and you're not really saving much typing. Could you describe in...
Is this still a problem?
Only the ones that are super-old and I suspect it might have already been fixed. Do you think this approach is incorrect somehow?
Eh, kinda disagree but fine. I'll confirm that I can't reproduce the issue and *then* slap on the label.
This reads like a dependabot report or something. Is there an actual problem with the current diff implementation that affects *your* usage of tree-sitter?
Having different tags for different types of releases sounds like madness. I've still not understood what exactly makes the library suitable to be part of the tree-sitter repo. As I...
I tested it, it took 80 ms for me to generate. Either you use a potato or this has been solved. Can you confirm?