thehowl
commented
1 year ago I guess I didn't specify it completely, but in #814's design stdshim loses its purpose :)
I address the part about precompilation in the second part of the proposal; but essentially I think that calls to native functions in gno code should simply call the Go function in the precompiled version, and if they require a *gno.Machine, then it is set to nil in the precompiled code, to indicate that this is outside of the normal gnovm execution.
So yes, in the "grand scheme" of things for my native bindings proposal, it would make sense to remove stdshim afterwards, as it wouldn't be used even for precompilation.
moul
piux2
Description
Shall we only name the files used by gvm as .gno? and move stdshim out of stdlibs?
https://github.com/gnolang/gno/tree/master/gnovm/stdlibs/stdshim
Files in stdlibs/stdshim are supposed to be temp go files generated from stdlibs/std/*.gno during the pre-compile process.
stdlibs/stdshim.go (not gno) is used to mock gno vm native function interface defined in stdlibs.go during gno precompile process so that precompile can use go build tools to check syntax and import path.
pre-compile and build are for developers to leverage the golang native build tool to check syntax and import during the gno development. GVM does not rely on anything from these optimizations or built outcomes.