Using Struct Tags to Control Encoding about ergo

[heri16]

Thanks for the quick response. It's amazing what this library could do if it takes off in the Elixir/Golang community.

We are using it to work with AWS services where the quality of the rust-native drivers are not yet production ready (to use with Rustler NIFs). The startup I work at is comfortable with Golang, but we know how much more productive a true functional language with pattern matching can be. So my sell to management is for Golang on the code paths were every extra ounce of performance is critical, combined with the robustness of OTP.

Will test out your fix over the weekend.

I'm also comfortable with golang so if you are open to contributions, let's formulate some guidelines.

[halturin]

etf.Term is just an interface type. You don't need it. What exactly are you trying to do?

[heri16]

I think I was looking for how go Structs can be converted to an etf.Map via annotations/tags just like the built-in json lib and aws-ion marshaller.

See: https://www.digitalocean.com/community/tutorials/how-to-use-struct-tags-in-go

[heri16]

We use *string extensively and ergo seems to crash when any nested value is a *string.

[halturin]

Hmm. It's a very interesting case. Actually, the value should be dereferenced during the encoding process.
https://github.com/halturin/ergo/blob/master/etf/encode.go#L547

I'll take a look closer.

[halturin]

created issue #65

[halturin]

I think I was looking for how go Structs can be converted to an etf.Map via annotations/tags just like the built-in json lib and aws-ion marshaller.

ETF encoder encodes any struct to the erlang map using field name as a key.
as an example this kind of value

type test struct {
	A string
}

will be encoded like this

#{'A' => "example"}

[halturin]

may I ask you to check out my fix of #65? just merged into the master

[halturin]

not valid any more