goluago

There are a number of Lisp interpreters written in Go [0-3]. There is a Lua interpreter [4]. The only compiled language I know is Gisp [5] by jcla1. I also built on top of Gisp with Gsp [6] to provide wrappers to the Go stdlib and support more standard lisp functionality. However, Kashimir is the first statically typed language implemented in Go that I have seen. The rest are dynamically typed. [0] GLISP - https://github.com/zhemao/glisp [1] golisp - https://github.com/SteelSeries/golisp [2] go-lisp - https://github.com/janne/go-lisp [3] Kakapo - https://github.com/bytbox/kakapo [4] Golua - https://github.com/akavel/goluago [5] Gisp - https://github.com/jcla1/gisp [6] Gsp - https://github.com/gsp-lang/gsp

Also some highly non-obvious gotchas and notes, straight from the trenches: - VERY IMPORTANT: you'll be actually writing for a pre-ANSI C compiler! Anything you think you know about C may prove false! Example real-world discrepancy found when porting Lua (an extremely high-quality ANSI C codebase) to Go's cc: http://golang.org/issue/7027 - The ternary operator (?:) is not supported on ARM (see: https://github.com/akavel/goluago/issues/8#issuecomment-4144...) - You don't have #if, #elif - You must be super careful, and really know what you're doing, when trying to pass pointers through the C<->Go boundary, as you're entering GC (garbage collector)'s carefully tended house of cards - You don't have access to the C standard library (although, see https://github.com/akavel/gostdc) - Using varargs functions is non-trivial - You must ensure you

If you are wanting a native dynamic scripting language for Go, goluago is coming along quite nicely (alpha version released at New Year): https://github.com/akavel/goluago I think if I wanted to implement a native Lisp interpreter/ bytecode compiler for Go, I would build on top of this project rather than starting from scratch.