The RPC and webserver/webclient approaches are well and good. Very standard, if high latency.
Other approaches I have used to extend Go dynamically: a) embed a scripting language: https://github.com/glycerine/zygomys (my lisp) https://github.com/google/starlark-go (a python with assign once semantics) https://awesome-go.com/embeddable-scripting-languages/ # a big long list of them https://github.com/glycerine/rmq # call from/embed R/talk to it over http b) embed a JIT/dynamic compiler https://github.com/gijit/gi # my partial implementation of Go on top of LuaJIT to get a REPL. Unfinished/has not been updated in many years. https://github.com/go-interpreter/chezgo -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/694f3128-c144-4bc0-854c-23e8b2ec9b94n%40googlegroups.com.
