Omit empty Creative>CreativeExtensions and InLine>Extensions

[jussi-kalliokoski]

Fixes #27. I don't really like this solution, but given how go marshals nested tags I couldn't come up with a better solution.

[rs]

@kalbasit please review

[kalbasit]

@rs LGTM

[louie432843]

@jussi-kalliokoski out of curiosity have you ever run across another way to deal with how go marshals nested tags other than using pointers to structs?

[jussi-kalliokoski]

@louie432843 unfortunately not, the XML marshal in go has remained relatively unchanged for a long time and I suspect the reason is that most use cases for go + XML are not very performance-sensitive (with a few exceptions, such as VAST ☹️ ). So the language probably considers it an OK tradeoff to take the performance hit for correctness (or to use template structs where you predefine all your would-be-pointers in structs so as to avoid the allocations, similar to how protobuf is often optimized where necessary) rather than to make improvements (breaking or otherwise) to the standard API.

[louie432843]

Thanks for the reply!