simplelanguage VS clj-kondo

That sort of stuff is easy to do with Truffle (which, ironically, lets you define a language using what they call the "truffle dsl").

The SimpleLanguage tutorial language has a bigint style number scheme with efficient optimization:

https://github.com/graalvm/simplelanguage/blob/master/langua...

Truffle has no opinion on how you parse the sources. It cares about how you execute them from an intermediate Truffle guided representation produced by the parser.

In other words antlr and truffle are a great fit. We even use this pairing for our example language simplelanguage.

https://github.com/graalvm/simplelanguage

Do you have any feedback on how we could improve the docs? If so, please let us know!

I believe the easiest way to start a new Truffle language implementation is to fork SimpleLanguage [1] and turn it into your language. Did you try to do that?

[1] https://github.com/graalvm/simplelanguage

Finally, I would suggest you to take a look at the Truffle/GraalVM ecosystem(https://www.graalvm.org/graalvm-as-a-platform/language-implementation-framework/). The documentation is not exactly very elaborate, but a few good resources are Mumbler(http://cesquivias.github.io/blog/2014/10/13/writing-a-language-in-truffle-part-1-a-simple-slow-interpreter/#mumbler-language), SimpleLanguage(https://github.com/graalvm/simplelanguage), and (https://www.endoflineblog.com/graal-truffle-tutorial-part-4-parsing-and-the-trufflelanguage-class).

My best suggestion here would be clj-kondo with flycheck-clj-kondo in Emacs. I really can't recommend it enough and would have killed to have it when I was learning Clojure. Not only will it underline all of those references to (now) undefined vars, but it can tell you about numerous little mistakes like mixing up arguments orders in (say) sequence functions, misplaced docstrings that get discarded, style conventions, etc. It's staggering how good it is even for a language as dynamic as Clojure.

The clj-kondo linters are worth reading.

Sure!

Spec: https://github.com/edn-format/edn

Example (linter config): https://github.com/clj-kondo/clj-kondo/blob/634294183a0aa2ca...

Clj-kondo doesn't produce an AST but you could easily combine the analysis output with the AST produced by rewrite-clj by matching on location.

But if you want full support, you can implement a hook: https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md

Please configure and use tools like clj-kondo and kibit. Kibit will report areas where you could write idiomatic clojure instead. Eg, it should catch all those (if (condition) true false) and ask you to replace it with (condition). Or if you really need a boolean value, use boolean to coerce it.

Try clj-kondo, a Clojure linter which will tell you about arity errors and more, before you even evaluate your code.