scriggo VS yaegi

We opened an issue for this, we'll work on it as soon as possible :)

Yes. There are long standing feature requests for (e.g.) the reflect package that simply don't get done because they'd break this assumption and/or force further indirection in hot paths to support "no code generation at runtime, ever".

Packages like Yaegi (that offers an interpreted Go REPL) have "know limitations, won't be addressed" also because of these assumptions.

https://github.com/golang/go/issues/4146

https://github.com/golang/go/issues/16522

https://github.com/traefik/yaegi?tab=readme-ov-file#limitati...

There is always https://github.com/traefik/yaegi - a Go interpreter written to make it easy to write plugins.

I think https://github.com/traefik/yaegi comes as close as using the python interpreter in you CLI, but for Go

There's a go interpreter: https://github.com/traefik/yaegi It could run programs without compiling them, but there're some limitations.

I'd recommend looking into a different approach for plugins such as hashicorp/go-plugin (which uses multiple process PIDs and RPC communication between them) or traefik/yaegi (which implements a Go-compatible scripting language that can be interpreted at runtime and which still supports most Go modules).

Why do we need a language like Rust when we have Rust. Why not just create a Rust interpreter. (There's such an interpreter for Go, BTW, https://github.com/traefik/yaegi )

A cool solution I saw was Traefik's yaegi module. They basically created an interpreted scripting language with Go compatible syntax (turning Go into an interpreted, not compiled, language). I haven't tried this but it sounds like it brings the better parts of dynamic languages like Python's plugin support to Go - plugin writers can still write "Go" code, which can load dynamically.