Add generic overloads to register and unregister value resolvers and comparers

[kevinkuszyk]

This is the PR for #1218.

As discussed there I've added generic overloads to register and unregister value resolvers and comparers.

I also updated:

• the code where the defaults are registered to use the new generic overloads where possible
• the worked example of using value resolvers and comparers.

If you'd prefer not not take the last two changes, I'll drop those commits.

When I was getting ready to push this code, I noticed @szaliszali has already made a start on this in #1260. I think I prefer the API changes there, but as noted they are breaking changes.

As this code was already done, I thought I may as well open a PR. If you prefer to go with the changes in #1260 thanks ok with me.

If you want to take this version, I'll update the changelog and docs.

Types of changes

• Bug fix (non-breaking change which fixes an issue).
• New feature (non-breaking change which adds functionality).
• Breaking change (fix or feature that would cause existing functionality to not work as expected).

Checklist:

• I've added tests for my code.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added an entry to the changelog

[SabotageAndi]

Is there a reason you didn't change these calls?

[kevinkuszyk]

I think those were the ones without parameterless constructors. I didn't want to make extra changes to those.

It's all moot point anyway now, as it looks like they've been updated #1273.

[SabotageAndi]

Thanks for the PR!
But I close it, because #1260 was chosen.

[kevinkuszyk]

No problem - I agree #1260 has a nicer api.