Thomas Pelletier

>Sweet! Whitespace would be awesome. Not sure how it could be stored - perhaps similarly to HeadComment/FootComment, you could potentially have a Leading/Trailing whitespace string. I'm going to play around...

Thanks for catching it, didn't mean to close this issue!

Thank you for the bug report! I'll take a look when I have time, but feel free to send a pull request in the meantime!

You're correct: this should be an error, because the array of tables is on `A.B`, and `B` is a struct, not a slice.

``` fuzz_test.go:31: INITIAL DOCUMENT =========================== fuzz_test.go:32: r=9999-12-31 23:59:60z fuzz_test.go:40: DECODED VALUE =========================== fuzz_test.go:41: map[string]interface {}{"r":time.Date(10000, time.January, 1, 0, 0, 0, 0, time.UTC)} fuzz_test.go:48: ENCODED DOCUMENT =========================== fuzz_test.go:49: r = 10000-01-01T00:00:00Z...

There seem to be two problems here: 1. Date time `9999-12-31 23:59:60z` is mapped to `10000-01-01 00:00:00z`, presumably because Go `time.Time` does not handle leap seconds and gets normalized by...

Thanks a lot for the analysis! I'm opting to emit an error when trying to parse a leap second. This seems less surprising than automatically mapping to the second after...

The answer to this question depends largely on what types are involved and the kind of operations you want to make. go-toml has support for [commented struct fields](https://github.com/pelletier/go-toml?tab=readme-ov-file#commented-config) ([example](https://pkg.go.dev/github.com/pelletier/go-toml/v2#example-Marshal-Commented)). You...

Closing this, feel free to open a [discussion](https://github.com/pelletier/go-toml/discussions) if there is more to discuss about this subject!

@boymaas Sorry for the late reply. We discussed it internally but forgot to reply back to this pull request. I do not want to continue expending the number of `df-*`...