3 ms·
@Borkdude I love your project & the name! I work on a similar tool (https://github.com/returntocorp/semgrep https://github.com/returntocorp/semgrep), we've rece
by ievans 6y ago
@Borkdude I love your project & the name! I work on a similar tool (https://github.com/returntocorp/semgrep https://github.com/returntocorp/semgrep), we've recently switched to using tree-sitter under the hood so that we can add new languages faster. Since Semgrep tries to support many languages, we can't use the native language parsers, so I was interested in https://github.com/sogaiu/tree-sitter-clojure https://github.com/sogaiu/tree-sitter-clojure. How mature vs buggy would you say the tree-sitter-clojure implementation is? We've found the quality of tree-sitter implementations can vary wildly across languages.
- Borkdude 6y agoSemgrep looks really interesting! I know the owner of that repo and I'll refer him to your question since he can answer this better than I can.
- Borkdude 6y agoResponse from the repo owner: it's unclear to me what exactly they rely on in tree-sitter grammars so it's hard to say whether tree-sitter-clojure would be helpful for them. i think tree-sitter-clojure does what it does pretty well based on testing across a large number of code files from clojars and recent generative testing runs. however, it deliberately does not try to do certain things (e.g. identify definitions, special forms, etc.) for various reasons. the approach is very similar to that of rewrite-clj* and parcera.