I'd guess an experimental Lisp interpreter embedded in Go is just too obvious :) But providing Gophers with a slightly more polished alternative that still com

I'd guess an experimental Lisp interpreter embedded in Go is just too obvious :) But providing Gophers with a slightly more polished alternative that still composes well with Go-code might help avoid the worst nightmares.