Thomas Pelletier

Hm at that point why not unmarshing into a an `interface{}` or `map[string]interface{}`? Is it to avoid a post-processing phase?

Thank you for the proposal! Sorry it took me a while to get back to you. I'm a little confused by https://github.com/opencontainers/image-spec/issues/1073#issuecomment-1589550392 this comment. Doesn't it mean that there is...

Ah got it. I didn't see the proposal in the first thread. If this proposal goes through, I'd be happy to have it implemented in go-toml! In the meantime, though,...

Hi! Thank you for the patch! However v1 is not supported anymore and will not receive any update. Consider using go-toml v2 instead.

Makes sense. I'd be happy to see a good patch to implement `toml.Unmarshaler` for v2! I think it would also help others (https://github.com/pelletier/go-toml/issues/857).

@ImSingee created https://github.com/pelletier/go-toml/issues/873 with some thoughts on the topic, hopefully it's helpful!

I'd love to support this. That kind of use case is exactly why I designed it with an intermediate AST as opposed to building structures straight from the parser. The...

> The issue I'm having is while building a KV map, I need to call NextExpression - eventually that will return something that's not in the KV map - and...

Sorry it took me so long to respond -- life gets in the way. Regarding storing comments: we can probably do something similar as go-yaml, though we would need to...

@mikefarah @TomWright I might have time this coming weekend to take a stab at having the parser keep comments and expose them on the AST (no promises 😇 ). If...