How are some of the micro functions being exported to lua?

[Neko-Box-Coder]

I am not too familiar with Go but can definitely read the code if pointed to the correct place.

As far as I know, the main two places of exporting functions (both micro and go itself) to Lua are in
internal/lua/lua.go and cmd/micro/initlua.go.

However, I am seeing there are some functions that are being exported to Lua without "explicitly" exporting them. For example the UpdateRules function

micro/internal/buffer/buffer.go

Line 784 in 55f45ce

func (b *Buffer) UpdateRules() {

which is used in one of the built-in plugins

micro/runtime/plugins/literate/literate.lua

Line 55 in 55f45ce

buf:UpdateRules()

Searching with the function name only gives me 5 places, and none of them are related to be exported to Lua.

So there should be some sort of "automatic" exporting in somewhere that automatically exports functions in a file, maybe?

Does anyone that is more familiar with Go can point me to the correct place(s) on where other functions are exported?

In addition to functions, how does Lua know the structure of a type in Go/micro? Again where are we exporting them?

[Andriamanitra]

You can use any public method on any object that you can access through one of the explicitly exported functions (or through event handler arguments).

[Neko-Box-Coder]

Thanks for the reply, so basically if there's an exported function that uses/returns the type buffer, it (ulua) will automatically export all the public functions that are associated (i.e. the type pointer after the function keyword and before the function name) with that type?

Or do you mean all the public functions in that file? (i.e. internal/buffer/buffer.go)

[Andriamanitra]

Just the functions that are associated with the type (called methods in Go). I don't know how the export works exactly but I think https://github.com/layeh/gopher-luar is the package that does it if you want to dig deeper.

[Neko-Box-Coder]

Cool, that makes a lot more sense now to me. Thanks a lot :)