Interop with local Go modules

[ivov]

From @lwintermelon at #11

What about just interop a local package or a package of go.work like a third-party one? It's quite pratical and easy to get started compared to incremental adoption alongside existing Go files. [...] For my case, no cgo or C FFI(even from purego). I have a pure go project, and I want to call it from new lisette code. Incremental adoption alongside existing Go files like Typescript and Javascript may be a long way to get. But lisette already has the ability to call third-party go packages now, what about my package?

[tacurran]

@lwintermelon would you mind making a psuedocode example of how you envision this in practice?