fix: handling of custom containers that has a TypeDefinition

[damien-robotsix]

Related to
#39 (comment)

Probably not the best way to solve it but it works for my application.

It might be a base to solve the issue.

[damien-robotsix]

Hello @henrygerardmoore can I ping you about this PR?

[henrygerardmoore]

Hello @henrygerardmoore can I ping you about this PR?

Yes sorry, let me review it this weekend 👍

[henrygerardmoore]

@damien-robotsix I made the branch add_custom_container_tests to add tests (even though they're basically just static asserts 😄). I mostly made this to make sure I understand the changes, could you take a look at that? I made a draft PR here (#56) just for easy reviewing, but feel free to merge those changes into this branch and we can continue to work off of this PR.

I think this shouldn't break any interfaces, correct? Unless, I suppose, someone was relying on the incorrect container overload for a custom type? Is that your understanding too?

In any case, thank you for the PR!

[henrygerardmoore]

@damien-robotsix does this seem correct to you? If so and if the merge conflict is resolved, I think this PR seems good to merge

I think this shouldn't break any interfaces, correct? Unless, I suppose, someone was relying on the incorrect container overload for a custom type? Is that your understanding too?

[damien-robotsix]

I just rebased on current main to allow merge

[damien-robotsix]

@henrygerardmoore Thank you