> > Hi, someone has the solution? > [...] Note that since 1.8 Go ignores tags on type conversions [1] so if you're actually dealing with an "XY problem" [2] -- trying to monkey-patch a struct type's tags at runtime to make it behave differently under different circumstances when (un)marshaling values of it -- you might consider defining two almost identical types which differ only in field tags¹ and use type conversions of values when (un)marshaling them in different ways.
¹ This can be done using code generation for instance; see `go help generate`. 1. https://beta.golang.org/doc/go1.8#language 2. http://xyproblem.info/ -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
