Yes, from the things they've chosen to compare. I am gomacro author's (gophernotes uses gomacro as Go interpreter) and I find the comparison needs an update. Among other things, gomacro now supports interfaces -…
For information, it's not the only Go kernel for Jupyter. There is also https://github.com/gopherdata/gophernotes which uses a different approach: contains a portable Go interpreter, instead of invoking the Go compiler…
It compiles a plugin for each Jupyter cell code with "go build -buildmode=plugin" then loads it. It's easy to see with Linux "lsof -p LGO_PID": it lists, among others, the loaded shared libraries - there is one per…
Hello d4l3k, I did not try go-pry yet, but I am very curious to compare it with my own attempt at an interactive Go REPL https://github.com/cosmos72/gomacro They look similar in several aspects, and different in some…
Yes, from the things they've chosen to compare. I am gomacro author's (gophernotes uses gomacro as Go interpreter) and I find the comparison needs an update. Among other things, gomacro now supports interfaces -…
For information, it's not the only Go kernel for Jupyter. There is also https://github.com/gopherdata/gophernotes which uses a different approach: contains a portable Go interpreter, instead of invoking the Go compiler…
It compiles a plugin for each Jupyter cell code with "go build -buildmode=plugin" then loads it. It's easy to see with Linux "lsof -p LGO_PID": it lists, among others, the loaded shared libraries - there is one per…
Hello d4l3k, I did not try go-pry yet, but I am very curious to compare it with my own attempt at an interactive Go REPL https://github.com/cosmos72/gomacro They look similar in several aspects, and different in some…