Proposal for a Go Interpreter

Re:Proposal for a Go Interpreter by zamalek on Monday September 07, 2015 @04:09AM (#10180517)

> To provide an interpreter that can embed inside a Go application, in order to provide scriptability to the Go ecosystem at large.

Can we move away from scripting engines at some point. They are big black boxes that you throw characters into and then "things" happen that you have no control over.

* What if I don't want the security?

* What if I want more security?

* What if I want actual pointers?

* What if I want to do one of a million things that don't fall into the original assumptions about what a Go interpreter would do?

Compiler-as-a-service is the future. A high quality parse tree, with a built-in interpreter or possibly JITter. Refactoring tools and tons of other cool things can be built instead of the same old black box.

If it's just going to be another plain-old interpreter, it would be best to instead focus on integrating V8 because a Go interpreter would bring far less to the table (notably interpreters are typically slow and one of the big benefits of Go is that it can be fast).

[ Parent | on HN ]

Re:Proposal for a Go Interpreter by justincormack on Monday September 07, 2015 @06:27AM (#10180866)

V8 is large and not actually that easy to embed. There is a pure Go implementation of Lua for scripting already [1]

[1] https://github.com/Shopify/go-lua

[ Parent | on HN ]

Re:Proposal for a Go Interpreter by ferbivore on Monday September 07, 2015 @11:45AM (#10181842)

There's also GopherLua [1], which is more active and supports features like coroutines and channels.

[1] https://github.com/yuin/gopher-lua

[ Parent | on HN ]

Re:Proposal for a Go Interpreter by sbinet on Monday September 07, 2015 @04:26AM (#10180549)

interesting, it's true having a toolbox for creating go interpreters would be much more powerful.

I am not sure I completely get what a compiler-as-a-service really is. could you expand please?

(wrt JITing, yes, we considered it and it's on our radar. we know some version of it worked at some point, at least at the proof-of-concept level: https://github.com/nelhage/gojit)

thanks for your input!

[ Parent | on HN ]

Re:Proposal for a Go Interpreter by zamalek on Monday September 07, 2015 @04:42AM (#10180582)

I suppose CAAS[1] doesn't make much sense outside of the .Net community :). The idea is that you very aggressively break down the compiler into the core constituent parts.

A less Microsoft-centric project would be Clang. Clang is quite accessible and despite that it's not as loosely coupled as Roslyn (e.g. I don't think you can refactor using it), you can still solve some real problems with it (such as autocomplete and static analysis).

Basically, CAAS is the front-end equivalent of LLVM. You turn the whole compiler into a very tidy API: following from that it should be significantly simpler to create something such as the interpreter that you are aiming for.

[1]: http://www.infoworld.com/article/2621132/microsoft-net/micro...

[ Parent | on HN ]

Re:Proposal for a Go Interpreter by sbinet on Monday September 07, 2015 @04:56AM (#10180613)

ah, didn't know about CAAS. of course LLVM/CLang was also on our radar. we are still pondering on whether we should target LLVM bitcode so we could easily build upon LLVM toolchain (and cross-pollinate with other LLVM-based interpreters. e.g. seamlessly interoperate with IJulia and CLing interpreters, sharing code and values at runtime thru LLVM.) to me, the main issue with LLVM is that it's a real pain to develop against, I know this for a fact having worked a little bit with CLing, the CLang-based C++ interpreter (the edit-compile-test cycle is that of a set of large C++ libraries, gophers tend to be spoiled in that department)

tangential: actually, you can refactor with the CLang libraries: http://llvm.org/releases/3.7.0/tools/clang/docs/LibTooling.h... (well, to some extent)

[ Parent | on HN ]

Re:Proposal for a Go Interpreter by amelius on Monday September 07, 2015 @04:17AM (#10180532)

+1 for the idea of integrating V8.

I tried using V8 from Go, but it turned out to be a performance-disaster mainly because the garbage collection strategy of Go requires objects in Go to be movable, hence all interactions between Go and V8 have to go through a lookup-table.

[ Parent | on HN ]

Re:Proposal for a Go Interpreter by current_call on Monday September 07, 2015 @02:53PM (#10182549)

Compiler-as-a-service is the future.

Lisp. You want Lisp.

[ Parent | on HN ]