Turiiya

> @ghost I saw that you referenced this issue in the task above. I could only see one item not checked there, but not related to this issue. The V...

Unfortunately, cannot into the issue due to missing reproduction steps. The experienced problem might be fixed with latest V already. Please leave a note if you experience further issues.

Yep, that would give most power to the user and ensure backwards compatibility. Would prorbaly make this PR mergable earlier as well. I'll look into it. Thanks @spytheman.

I have looked into this a bit. Calling these methods when they are defined, but keeping them optional to allow automatic handling adds some complexity. The only way I can...

To throw in some thoughts: Is a customized decoding/encoding inside the modules `toml.decode` / `toml.enocode` even a desired thing? It would still be possible after all. Users could define toml...

> Imho the support for custom .from_toml and .to_toml methods should stay - if they are defined, they should be tried first, and if they are not, the toml module...

To much wine yesterday. Thanks @spytheman. I updated the method test to include custom encoding logic to cause failiure if the methods won't be used.

> As an example; It'll be impossible to know what format to decode to. Does the user want: Agreed @Larpon. I won't try to crack the nut of satisfying custom...

@Larpon en-/decoding of nested structs and arrays was added. Now it already got hacky. So if a moment in your schedule frees up, I'd like to know your opinion on...

Thanks for the review. I think I also had some improvements in mind. I will have another look at it tomorrow as well 👍 Have a good evening!