stdlib

It may be a naive quesiton, but what does "prelude" mean in this context? I get that I can use this to emit go code from gisp, and compile that. But the example under the heading "using the prelude" doesn't really tell me anything. Looking at the code, it appears to define a lot of basic lisp stuff -- but without all that, how does gsp work in the first place? Is it simply the difference of wrapping things up so that they... work?: diff <(gsp hello.gsp) <(gisp hello.gsp) 4,7c4,5 < "github.com/gsp-lang/stdlib/fmt" < "github.com/gsp-lang/gsp/core" < "github.com/gsp-lang/stdlib/prelude" < "github.com/gsp-lang/stdlib/net/http" --- > "/fmt" > "/net/http" 18,19d15 < < var _ = prelude.Len As far as I can tell, gisp doesn't produce go code that can be compiled.

You should be able to reach any Go library, in fact. Aside from the Prelude, the Gsp Stdlib[0] is in fact just bindings to the Go stdlib that casts every value from interface{} into the required type. You can make bindings to any other library in this manner. I do not know why Go-routines would not work, though I have not tried yet. Another difference from the lisp you brought up (and the one I'm more familiar with, glisp[1]) is that Gsp is compiled as opposed to interpreted. This would ostensibly have speed features. I am interested to test how this fares compared to these other Go Lisps and Clojure. [0] https://github.com/gsp-lang/stdlib [1] https://github.com/zhemao/glisp