funcgo

Update: The new 0.4.0 release of Funcgo supports limited operator overloading: https://github.com/eobrain/funcgo/blob/master/doc/reference....

Thanks all. I created a new FAQ page for Funcgo, seeded with the questions and answers from this forum. https://github.com/eobrain/funcgo/blob/master/doc/FAQ.md

Glad to hear someone else has been thinking about this. Interesting idea to use macros to implement the mapping from the Go syntax tree. Presumably, these macros would implement the same kind of logic that my codegen module implements (mapping from the Go syntax tree to Clojure text). https://github.com/eobrain/funcgo/blob/master/src/funcgo/cod...

I have plans to implement source maps https://github.com/eobrain/funcgo/issues/19 when targeting JavaScript I have not yet figured out the best way to do something equivalent when targeting the JVM. This is one of several toolchain issues. In addition to stabilizing the language itself, getting a smooth toolchain is the biggest thing left to do before a 1.0 release of Funcgo. (Though it is worth noting that Coffeescript, an analogous language, got widespread adoption before tackling the source location issue.)

I've no immediate plans for another target for now – there is a lot of work still to do just targeting Clojure and making sure the toolchain is easy for programmers, both server-side and client side. As regards typing, Funcgo has type inference using Clojure's type-hinting and it can use all of Clojures immutable collections as well as the standard Java mutable collections. As for operator overloading, it's not there yet, but I just I added a user story (https://github.com/eobrain/funcgo/issues/18) to my backlog to allow function names to be operators (like in Scala). However it won't really be operator overloading because the underlying Clojure only allows overloading by arity, not by type.